* Acer Aspire 1705SMi LNKx?
@ 2004-10-25 8:09 Oisín Mac Fhearaí
[not found] ` <200410250909.41761.destynova-iUB+o6dfpG8i1yMB4YHZDQ@public.gmane.org>
0 siblings, 1 reply; 12+ messages in thread
From: Oisín Mac Fhearaí @ 2004-10-25 8:09 UTC (permalink / raw)
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f
I finally got around to compiling in my custom DSDT for my Acer Aspire 1705SMi
laptop, and have battery giving useful information now.
However, there's still some somewhat confusing messages at bootup; can anyone
shed some light on this - is it bad/fixable?
PCI: Ignoring BAR0-3 of IDE controller 0000:00:02.5
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT]
uteval-0205: *** Error: Return object type is incorrect
[\_SB_.PCI0.LPCB.LNKA._CRS] (Node dfdeb7a8), AE_TYPE
ACPI: PCI Interrupt Link [LNKA] (IRQs 7 10) *0
ACPI: PCI Interrupt Link [LNKB] (IRQs 3) *0, disabled.
uteval-0205: *** Error: Return object type is incorrect
[\_SB_.PCI0.LPCB.LNKC._CRS] (Node dfde93a8), AE_TYPE
ACPI: PCI Interrupt Link [LNKC] (IRQs 5) *0
uteval-0205: *** Error: Return object type is incorrect
[\_SB_.PCI0.LPCB.LNKD._CRS] (Node dfde91a8), AE_TYPE
ACPI: PCI Interrupt Link [LNKD] (IRQs 7 10) *0
uteval-0205: *** Error: Return object type is incorrect
[\_SB_.PCI0.LPCB.LNKE._CRS] (Node dfdeaea8), AE_TYPE
ACPI: PCI Interrupt Link [LNKE] (IRQs 7 10) *0
uteval-0205: *** Error: Return object type is incorrect
[\_SB_.PCI0.LPCB.LNKF._CRS] (Node dfdeaca8), AE_TYPE
ACPI: PCI Interrupt Link [LNKF] (IRQs 7 10) *0
uteval-0205: *** Error: Return object type is incorrect
[\_SB_.PCI0.LPCB.LNKG._CRS] (Node dfdeaaa8), AE_TYPE
ACPI: PCI Interrupt Link [LNKG] (IRQs 7 10) *0
ACPI: PCI Interrupt Link [LNKH] (IRQs 7 10) *0, disabled.
The portions of the DSDT in question are like this (in this instance, in
Device (LNKA)):
Method (_CRS, 0, NotSerialized)
{
Store (Z00B, Local0)
CreateWordField (Local0, 0x01, IRA0)
If (LEqual (And (\_SB.PCI0.LPCB.PIRA, 0x80), Zero))
{
And (\_SB.PCI0.LPCB.PIRA, 0x0F, Local0)
ShiftLeft (0x01, Local0, IRA0)
}
Else
{
Store (0x00, IRA0)
}
Return (Local0)
}
Oisín
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Acer Aspire 1705SMi LNKx?
[not found] ` <200410250909.41761.destynova-iUB+o6dfpG8i1yMB4YHZDQ@public.gmane.org>
@ 2004-10-25 14:30 ` Patrick Ale
0 siblings, 0 replies; 12+ messages in thread
From: Patrick Ale @ 2004-10-25 14:30 UTC (permalink / raw)
To: Oisín Mac Fhearaí; +Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f
Hello,
I'd be interested in the answer on this question aswell.
On my Aspire 1703SM battery, temperature reading et all is working now
(long live boring sundays where one has nothing better to do than
drinking coffee and try to fix stuff).
If anyone is interested in the modified DSDT I am using now, please
send me an email and I'll hook you up.
BIG PHAT WARNING: DO NOT, and again I repeat DO NOT use ANY of the
1703 series DSDT from the repository on acpi.sourceforge.net. The DSDT
for the SMi and SCME will do stuff that you dont want, like 50 ACPI
errors in your syslog every second or a temperature that says 255C.
The modifications to the DSDT of the 1703SM ARE the same as the ones
in the repository, just on different lines of the dsl file.
Thanks for all the people that helped me out.
Patrick
On Mon, 25 Oct 2004 09:09:41 +0100, Oisín Mac Fhearaí
<destynova-iUB+o6dfpG8i1yMB4YHZDQ@public.gmane.org> wrote:
> I finally got around to compiling in my custom DSDT for my Acer Aspire 1705SMi
> laptop, and have battery giving useful information now.
>
> However, there's still some somewhat confusing messages at bootup; can anyone
> shed some light on this - is it bad/fixable?
>
> PCI: Ignoring BAR0-3 of IDE controller 0000:00:02.5
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT]
> uteval-0205: *** Error: Return object type is incorrect
> [\_SB_.PCI0.LPCB.LNKA._CRS] (Node dfdeb7a8), AE_TYPE
> ACPI: PCI Interrupt Link [LNKA] (IRQs 7 10) *0
> ACPI: PCI Interrupt Link [LNKB] (IRQs 3) *0, disabled.
> uteval-0205: *** Error: Return object type is incorrect
> [\_SB_.PCI0.LPCB.LNKC._CRS] (Node dfde93a8), AE_TYPE
> ACPI: PCI Interrupt Link [LNKC] (IRQs 5) *0
> uteval-0205: *** Error: Return object type is incorrect
> [\_SB_.PCI0.LPCB.LNKD._CRS] (Node dfde91a8), AE_TYPE
> ACPI: PCI Interrupt Link [LNKD] (IRQs 7 10) *0
> uteval-0205: *** Error: Return object type is incorrect
> [\_SB_.PCI0.LPCB.LNKE._CRS] (Node dfdeaea8), AE_TYPE
> ACPI: PCI Interrupt Link [LNKE] (IRQs 7 10) *0
> uteval-0205: *** Error: Return object type is incorrect
> [\_SB_.PCI0.LPCB.LNKF._CRS] (Node dfdeaca8), AE_TYPE
> ACPI: PCI Interrupt Link [LNKF] (IRQs 7 10) *0
> uteval-0205: *** Error: Return object type is incorrect
> [\_SB_.PCI0.LPCB.LNKG._CRS] (Node dfdeaaa8), AE_TYPE
> ACPI: PCI Interrupt Link [LNKG] (IRQs 7 10) *0
> ACPI: PCI Interrupt Link [LNKH] (IRQs 7 10) *0, disabled.
>
> The portions of the DSDT in question are like this (in this instance, in
> Device (LNKA)):
>
> Method (_CRS, 0, NotSerialized)
> {
> Store (Z00B, Local0)
> CreateWordField (Local0, 0x01, IRA0)
> If (LEqual (And (\_SB.PCI0.LPCB.PIRA, 0x80), Zero))
> {
> And (\_SB.PCI0.LPCB.PIRA, 0x0F, Local0)
> ShiftLeft (0x01, Local0, IRA0)
> }
> Else
> {
> Store (0x00, IRA0)
> }
>
> Return (Local0)
> }
>
> Oisín
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Acpi-devel mailing list
> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/acpi-devel
>
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
^ permalink raw reply [flat|nested] 12+ messages in thread
* RE: Acer Aspire 1705SMi LNKx?
@ 2004-10-25 15:52 Yu, Luming
2004-10-25 19:10 ` Patrick Ale
2004-10-25 21:47 ` Oisín Mac Fhearaí
0 siblings, 2 replies; 12+ messages in thread
From: Yu, Luming @ 2004-10-25 15:52 UTC (permalink / raw)
To: Patrick Ale, Oisín Mac Fhearaí
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f
It's nice to hear that you have fixed the buggy DSDT.
But I want to say MS windows should be ok with
the original DSDT, which breaks linux somehow.
To make sure linux can live with the original one,
I think we need to identify the quirks in the specific box, that
we can take into linux acpi for the sake of compatibility.
So, please give a brief description on what you did.
Thanks
Luming
>-----Original Message-----
>From: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>[mailto:acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf Of
>Patrick Ale
>Sent: 2004年10月25日 22:31
>To: Oisín Mac Fhearaí
>Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>Subject: Re: [ACPI] Acer Aspire 1705SMi LNKx?
>
>Hello,
>
>I'd be interested in the answer on this question aswell.
>On my Aspire 1703SM battery, temperature reading et all is working now
>(long live boring sundays where one has nothing better to do than
>drinking coffee and try to fix stuff).
>
>If anyone is interested in the modified DSDT I am using now, please
>send me an email and I'll hook you up.
>
>BIG PHAT WARNING: DO NOT, and again I repeat DO NOT use ANY of the
>1703 series DSDT from the repository on acpi.sourceforge.net. The DSDT
>for the SMi and SCME will do stuff that you dont want, like 50 ACPI
>errors in your syslog every second or a temperature that says 255C.
>
>The modifications to the DSDT of the 1703SM ARE the same as the ones
>in the repository, just on different lines of the dsl file.
>
>
>Thanks for all the people that helped me out.
>
>Patrick
>
>
>On Mon, 25 Oct 2004 09:09:41 +0100, Oisín Mac Fhearaí
><destynova-iUB+o6dfpG8i1yMB4YHZDQ@public.gmane.org> wrote:
>> I finally got around to compiling in my custom DSDT for my
>Acer Aspire 1705SMi
>> laptop, and have battery giving useful information now.
>>
>> However, there's still some somewhat confusing messages at
>bootup; can anyone
>> shed some light on this - is it bad/fixable?
>>
>> PCI: Ignoring BAR0-3 of IDE controller 0000:00:02.5
>> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
>> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT]
>> uteval-0205: *** Error: Return object type is incorrect
>> [\_SB_.PCI0.LPCB.LNKA._CRS] (Node dfdeb7a8), AE_TYPE
>> ACPI: PCI Interrupt Link [LNKA] (IRQs 7 10) *0
>> ACPI: PCI Interrupt Link [LNKB] (IRQs 3) *0, disabled.
>> uteval-0205: *** Error: Return object type is incorrect
>> [\_SB_.PCI0.LPCB.LNKC._CRS] (Node dfde93a8), AE_TYPE
>> ACPI: PCI Interrupt Link [LNKC] (IRQs 5) *0
>> uteval-0205: *** Error: Return object type is incorrect
>> [\_SB_.PCI0.LPCB.LNKD._CRS] (Node dfde91a8), AE_TYPE
>> ACPI: PCI Interrupt Link [LNKD] (IRQs 7 10) *0
>> uteval-0205: *** Error: Return object type is incorrect
>> [\_SB_.PCI0.LPCB.LNKE._CRS] (Node dfdeaea8), AE_TYPE
>> ACPI: PCI Interrupt Link [LNKE] (IRQs 7 10) *0
>> uteval-0205: *** Error: Return object type is incorrect
>> [\_SB_.PCI0.LPCB.LNKF._CRS] (Node dfdeaca8), AE_TYPE
>> ACPI: PCI Interrupt Link [LNKF] (IRQs 7 10) *0
>> uteval-0205: *** Error: Return object type is incorrect
>> [\_SB_.PCI0.LPCB.LNKG._CRS] (Node dfdeaaa8), AE_TYPE
>> ACPI: PCI Interrupt Link [LNKG] (IRQs 7 10) *0
>> ACPI: PCI Interrupt Link [LNKH] (IRQs 7 10) *0, disabled.
>>
>> The portions of the DSDT in question are like this (in this
>instance, in
>> Device (LNKA)):
>>
>> Method (_CRS, 0, NotSerialized)
>> {
>> Store (Z00B, Local0)
>> CreateWordField (Local0, 0x01, IRA0)
>> If (LEqual (And
>(\_SB.PCI0.LPCB.PIRA, 0x80), Zero))
>> {
>> And (\_SB.PCI0.LPCB.PIRA, 0x0F, Local0)
>> ShiftLeft (0x01, Local0, IRA0)
>> }
>> Else
>> {
>> Store (0x00, IRA0)
>> }
>>
>> Return (Local0)
>> }
>>
>> Oisín
>>
>> -------------------------------------------------------
>> This SF.net email is sponsored by: IT Product Guide on
>ITManagersJournal
>> Use IT products in your business? Tell us what you think of
>them. Give us
>> Your Opinions, Get Free ThinkGeek Gift Certificates! Click
>to find out more
>> http://productguide.itmanagersjournal.com/guidepromo.tmpl
>> _______________________________________________
>> Acpi-devel mailing list
>> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>> https://lists.sourceforge.net/lists/listinfo/acpi-devel
>>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: IT Product Guide on
>ITManagersJournal
>Use IT products in your business? Tell us what you think of
>them. Give us
>Your Opinions, Get Free ThinkGeek Gift Certificates! Click to
>find out more
>http://productguide.itmanagersjournal.com/guidepromo.tmpl
>_______________________________________________
>Acpi-devel mailing list
>Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>https://lists.sourceforge.net/lists/listinfo/acpi-devel
>
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Acer Aspire 1705SMi LNKx?
2004-10-25 15:52 Acer Aspire 1705SMi LNKx? Yu, Luming
@ 2004-10-25 19:10 ` Patrick Ale
[not found] ` <8d158e1f04102512101b5808e2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2004-10-25 21:47 ` Oisín Mac Fhearaí
1 sibling, 1 reply; 12+ messages in thread
From: Patrick Ale @ 2004-10-25 19:10 UTC (permalink / raw)
To: Yu, Luming
Cc: Oisín Mac Fhearaí,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f
Hi,
I can send you the output of a "diff -u5" so you can see what I did if
you llike.
Next to the DSDT changes I patched my vanilla 2.6.9 kernel with the
latest Alax Cox patch (-ac4) which also solved the last errors about
the LNKx errors. So my guess is that it is both an DSDT plus an kernel
issue.
Maybe Windows has some nifty way of not needing the exact/specific
adresses for hardware/functionality, I dunno, I am not a programmer :D
Let me know if you want the diff file and i'll send you right away.
Cheers,
Patrick
On Mon, 25 Oct 2004 23:52:27 +0800, Yu, Luming <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> wrote:
> It's nice to hear that you have fixed the buggy DSDT.
> But I want to say MS windows should be ok with
> the original DSDT, which breaks linux somehow.
> To make sure linux can live with the original one,
> I think we need to identify the quirks in the specific box, that
> we can take into linux acpi for the sake of compatibility.
> So, please give a brief description on what you did.
>
> Thanks
> Luming
>
>
>
> >-----Original Message-----
> >From: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> >[mailto:acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf Of
> >Patrick Ale
> >Sent: 2004年10月25日 22:31
> >To: Oisín Mac Fhearaí
> >Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> >Subject: Re: [ACPI] Acer Aspire 1705SMi LNKx?
> >
> >Hello,
> >
> >I'd be interested in the answer on this question aswell.
> >On my Aspire 1703SM battery, temperature reading et all is working now
> >(long live boring sundays where one has nothing better to do than
> >drinking coffee and try to fix stuff).
> >
> >If anyone is interested in the modified DSDT I am using now, please
> >send me an email and I'll hook you up.
> >
> >BIG PHAT WARNING: DO NOT, and again I repeat DO NOT use ANY of the
> >1703 series DSDT from the repository on acpi.sourceforge.net. The DSDT
> >for the SMi and SCME will do stuff that you dont want, like 50 ACPI
> >errors in your syslog every second or a temperature that says 255C.
> >
> >The modifications to the DSDT of the 1703SM ARE the same as the ones
> >in the repository, just on different lines of the dsl file.
> >
> >
> >Thanks for all the people that helped me out.
> >
> >Patrick
> >
> >
> >On Mon, 25 Oct 2004 09:09:41 +0100, Oisín Mac Fhearaí
> ><destynova-iUB+o6dfpG8i1yMB4YHZDQ@public.gmane.org> wrote:
> >> I finally got around to compiling in my custom DSDT for my
> >Acer Aspire 1705SMi
> >> laptop, and have battery giving useful information now.
> >>
> >> However, there's still some somewhat confusing messages at
> >bootup; can anyone
> >> shed some light on this - is it bad/fixable?
> >>
> >> PCI: Ignoring BAR0-3 of IDE controller 0000:00:02.5
> >> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
> >> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT]
> >> uteval-0205: *** Error: Return object type is incorrect
> >> [\_SB_.PCI0.LPCB.LNKA._CRS] (Node dfdeb7a8), AE_TYPE
> >> ACPI: PCI Interrupt Link [LNKA] (IRQs 7 10) *0
> >> ACPI: PCI Interrupt Link [LNKB] (IRQs 3) *0, disabled.
> >> uteval-0205: *** Error: Return object type is incorrect
> >> [\_SB_.PCI0.LPCB.LNKC._CRS] (Node dfde93a8), AE_TYPE
> >> ACPI: PCI Interrupt Link [LNKC] (IRQs 5) *0
> >> uteval-0205: *** Error: Return object type is incorrect
> >> [\_SB_.PCI0.LPCB.LNKD._CRS] (Node dfde91a8), AE_TYPE
> >> ACPI: PCI Interrupt Link [LNKD] (IRQs 7 10) *0
> >> uteval-0205: *** Error: Return object type is incorrect
> >> [\_SB_.PCI0.LPCB.LNKE._CRS] (Node dfdeaea8), AE_TYPE
> >> ACPI: PCI Interrupt Link [LNKE] (IRQs 7 10) *0
> >> uteval-0205: *** Error: Return object type is incorrect
> >> [\_SB_.PCI0.LPCB.LNKF._CRS] (Node dfdeaca8), AE_TYPE
> >> ACPI: PCI Interrupt Link [LNKF] (IRQs 7 10) *0
> >> uteval-0205: *** Error: Return object type is incorrect
> >> [\_SB_.PCI0.LPCB.LNKG._CRS] (Node dfdeaaa8), AE_TYPE
> >> ACPI: PCI Interrupt Link [LNKG] (IRQs 7 10) *0
> >> ACPI: PCI Interrupt Link [LNKH] (IRQs 7 10) *0, disabled.
> >>
> >> The portions of the DSDT in question are like this (in this
> >instance, in
> >> Device (LNKA)):
> >>
> >> Method (_CRS, 0, NotSerialized)
> >> {
> >> Store (Z00B, Local0)
> >> CreateWordField (Local0, 0x01, IRA0)
> >> If (LEqual (And
> >(\_SB.PCI0.LPCB.PIRA, 0x80), Zero))
> >> {
> >> And (\_SB.PCI0.LPCB.PIRA, 0x0F, Local0)
> >> ShiftLeft (0x01, Local0, IRA0)
> >> }
> >> Else
> >> {
> >> Store (0x00, IRA0)
> >> }
> >>
> >> Return (Local0)
> >> }
> >>
> >> Oisín
> >>
> >> -------------------------------------------------------
> >> This SF.net email is sponsored by: IT Product Guide on
> >ITManagersJournal
> >> Use IT products in your business? Tell us what you think of
> >them. Give us
> >> Your Opinions, Get Free ThinkGeek Gift Certificates! Click
> >to find out more
> >> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> >> _______________________________________________
> >> Acpi-devel mailing list
> >> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> >> https://lists.sourceforge.net/lists/listinfo/acpi-devel
> >>
> >
> >
> >-------------------------------------------------------
> >This SF.net email is sponsored by: IT Product Guide on
> >ITManagersJournal
> >Use IT products in your business? Tell us what you think of
> >them. Give us
> >Your Opinions, Get Free ThinkGeek Gift Certificates! Click to
> >find out more
> >http://productguide.itmanagersjournal.com/guidepromo.tmpl
> >_______________________________________________
> >Acpi-devel mailing list
> >Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> >https://lists.sourceforge.net/lists/listinfo/acpi-devel
> >
>
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Acer Aspire 1705SMi LNKx?
[not found] ` <8d158e1f04102512101b5808e2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
@ 2004-10-25 19:18 ` Patrick Ale
0 siblings, 0 replies; 12+ messages in thread
From: Patrick Ale @ 2004-10-25 19:18 UTC (permalink / raw)
To: Yu, Luming
Cc: Oisín Mac Fhearaí,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f
Forget the "last errors fixed" part in my last email. I still see them :(
Everything seems to work tho so I have no idea what this error is about.
Patrick
On Mon, 25 Oct 2004 21:10:41 +0200, Patrick Ale <patrick.ale-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Hi,
>
> I can send you the output of a "diff -u5" so you can see what I did if
> you llike.
> Next to the DSDT changes I patched my vanilla 2.6.9 kernel with the
> latest Alax Cox patch (-ac4) which also solved the last errors about
> the LNKx errors. So my guess is that it is both an DSDT plus an kernel
> issue.
>
> Maybe Windows has some nifty way of not needing the exact/specific
> adresses for hardware/functionality, I dunno, I am not a programmer :D
>
> Let me know if you want the diff file and i'll send you right away.
>
> Cheers,
>
>
>
> Patrick
>
> On Mon, 25 Oct 2004 23:52:27 +0800, Yu, Luming <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> wrote:
> > It's nice to hear that you have fixed the buggy DSDT.
> > But I want to say MS windows should be ok with
> > the original DSDT, which breaks linux somehow.
> > To make sure linux can live with the original one,
> > I think we need to identify the quirks in the specific box, that
> > we can take into linux acpi for the sake of compatibility.
> > So, please give a brief description on what you did.
> >
> > Thanks
> > Luming
> >
> >
> >
> > >-----Original Message-----
> > >From: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> > >[mailto:acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf Of
> > >Patrick Ale
> > >Sent: 2004年10月25日 22:31
> > >To: Oisín Mac Fhearaí
> > >Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> > >Subject: Re: [ACPI] Acer Aspire 1705SMi LNKx?
> > >
> > >Hello,
> > >
> > >I'd be interested in the answer on this question aswell.
> > >On my Aspire 1703SM battery, temperature reading et all is working now
> > >(long live boring sundays where one has nothing better to do than
> > >drinking coffee and try to fix stuff).
> > >
> > >If anyone is interested in the modified DSDT I am using now, please
> > >send me an email and I'll hook you up.
> > >
> > >BIG PHAT WARNING: DO NOT, and again I repeat DO NOT use ANY of the
> > >1703 series DSDT from the repository on acpi.sourceforge.net. The DSDT
> > >for the SMi and SCME will do stuff that you dont want, like 50 ACPI
> > >errors in your syslog every second or a temperature that says 255C.
> > >
> > >The modifications to the DSDT of the 1703SM ARE the same as the ones
> > >in the repository, just on different lines of the dsl file.
> > >
> > >
> > >Thanks for all the people that helped me out.
> > >
> > >Patrick
> > >
> > >
> > >On Mon, 25 Oct 2004 09:09:41 +0100, Oisín Mac Fhearaí
> > ><destynova-iUB+o6dfpG8i1yMB4YHZDQ@public.gmane.org> wrote:
> > >> I finally got around to compiling in my custom DSDT for my
> > >Acer Aspire 1705SMi
> > >> laptop, and have battery giving useful information now.
> > >>
> > >> However, there's still some somewhat confusing messages at
> > >bootup; can anyone
> > >> shed some light on this - is it bad/fixable?
> > >>
> > >> PCI: Ignoring BAR0-3 of IDE controller 0000:00:02.5
> > >> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
> > >> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT]
> > >> uteval-0205: *** Error: Return object type is incorrect
> > >> [\_SB_.PCI0.LPCB.LNKA._CRS] (Node dfdeb7a8), AE_TYPE
> > >> ACPI: PCI Interrupt Link [LNKA] (IRQs 7 10) *0
> > >> ACPI: PCI Interrupt Link [LNKB] (IRQs 3) *0, disabled.
> > >> uteval-0205: *** Error: Return object type is incorrect
> > >> [\_SB_.PCI0.LPCB.LNKC._CRS] (Node dfde93a8), AE_TYPE
> > >> ACPI: PCI Interrupt Link [LNKC] (IRQs 5) *0
> > >> uteval-0205: *** Error: Return object type is incorrect
> > >> [\_SB_.PCI0.LPCB.LNKD._CRS] (Node dfde91a8), AE_TYPE
> > >> ACPI: PCI Interrupt Link [LNKD] (IRQs 7 10) *0
> > >> uteval-0205: *** Error: Return object type is incorrect
> > >> [\_SB_.PCI0.LPCB.LNKE._CRS] (Node dfdeaea8), AE_TYPE
> > >> ACPI: PCI Interrupt Link [LNKE] (IRQs 7 10) *0
> > >> uteval-0205: *** Error: Return object type is incorrect
> > >> [\_SB_.PCI0.LPCB.LNKF._CRS] (Node dfdeaca8), AE_TYPE
> > >> ACPI: PCI Interrupt Link [LNKF] (IRQs 7 10) *0
> > >> uteval-0205: *** Error: Return object type is incorrect
> > >> [\_SB_.PCI0.LPCB.LNKG._CRS] (Node dfdeaaa8), AE_TYPE
> > >> ACPI: PCI Interrupt Link [LNKG] (IRQs 7 10) *0
> > >> ACPI: PCI Interrupt Link [LNKH] (IRQs 7 10) *0, disabled.
> > >>
> > >> The portions of the DSDT in question are like this (in this
> > >instance, in
> > >> Device (LNKA)):
> > >>
> > >> Method (_CRS, 0, NotSerialized)
> > >> {
> > >> Store (Z00B, Local0)
> > >> CreateWordField (Local0, 0x01, IRA0)
> > >> If (LEqual (And
> > >(\_SB.PCI0.LPCB.PIRA, 0x80), Zero))
> > >> {
> > >> And (\_SB.PCI0.LPCB.PIRA, 0x0F, Local0)
> > >> ShiftLeft (0x01, Local0, IRA0)
> > >> }
> > >> Else
> > >> {
> > >> Store (0x00, IRA0)
> > >> }
> > >>
> > >> Return (Local0)
> > >> }
> > >>
> > >> Oisín
> > >>
> > >> -------------------------------------------------------
> > >> This SF.net email is sponsored by: IT Product Guide on
> > >ITManagersJournal
> > >> Use IT products in your business? Tell us what you think of
> > >them. Give us
> > >> Your Opinions, Get Free ThinkGeek Gift Certificates! Click
> > >to find out more
> > >> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> > >> _______________________________________________
> > >> Acpi-devel mailing list
> > >> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> > >> https://lists.sourceforge.net/lists/listinfo/acpi-devel
> > >>
> > >
> > >
> > >-------------------------------------------------------
> > >This SF.net email is sponsored by: IT Product Guide on
> > >ITManagersJournal
> > >Use IT products in your business? Tell us what you think of
> > >them. Give us
> > >Your Opinions, Get Free ThinkGeek Gift Certificates! Click to
> > >find out more
> > >http://productguide.itmanagersjournal.com/guidepromo.tmpl
> > >_______________________________________________
> > >Acpi-devel mailing list
> > >Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> > >https://lists.sourceforge.net/lists/listinfo/acpi-devel
> > >
> >
>
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Acer Aspire 1705SMi LNKx?
2004-10-25 15:52 Acer Aspire 1705SMi LNKx? Yu, Luming
2004-10-25 19:10 ` Patrick Ale
@ 2004-10-25 21:47 ` Oisín Mac Fhearaí
[not found] ` <200410252247.39042.destynova-iUB+o6dfpG8i1yMB4YHZDQ@public.gmane.org>
1 sibling, 1 reply; 12+ messages in thread
From: Oisín Mac Fhearaí @ 2004-10-25 21:47 UTC (permalink / raw)
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f; +Cc: Yu, Luming
[-- Attachment #1: Type: text/plain, Size: 3687 bytes --]
On Monday 25 October 2004 16:52, Yu, Luming wrote:
> It's nice to hear that you have fixed the buggy DSDT.
> But I want to say MS windows should be ok with
> the original DSDT, which breaks linux somehow.
> To make sure linux can live with the original one,
> I think we need to identify the quirks in the specific box, that
> we can take into linux acpi for the sake of compatibility.
> So, please give a brief description on what you did.
>
> Thanks
> Luming
The thing that worries me a little about this is, as time goes by and you
create workarounds in the ACPI code (as, presumably, Windows has) for machine
specific behaviour, will we end up with a constantly growing mess of code to
handle them all, or will workarounds be phased out in favour of proper fixes?
I've uploaded the original binary dsdt, disassembled version (which I did
using quite an old version of iasl) and fixed version to
http://www.redbrick.dcu.ie/~exolon/dsdt , /dsdt.dsl and /fixed.dsl
respectively.
Here is the -U5 diff for summary. The fixes I used were all standard except
for the Z00D problem. I found no references to Z00D in any of the tables
supplied by the machine, so using a fixed version uploaded to the dsdt
repository, replaced them with Z00C. Robert Moore mentioned that these values
may get overwritten anyway and 0 would also have worked, so I suppose it
doesn't matter. :)
good luck,
Oisín
___
--- dsdt.dsl 2004-10-25 22:11:22.501511136 +0100
+++ fixed.dsl 2004-10-25 22:11:03.349422696 +0100
@@ -1,10 +1,10 @@
/*
* Intel ACPI Component Architecture
- * AML Disassembler version 20040715
+ * AML Disassembler version 20030918
*
- * Disassembly of dsdt, Mon Oct 25 22:11:22 2004
+ * Disassembly of dsdt, Mon Aug 30 08:05:46 2004
*/
DefinitionBlock ("DSDT.aml", "DSDT", 1, "PTLTD ", "650M", 100925440)
{
OperationRegion (P80G, SystemIO, 0x80, 0x01)
Field (P80G, ByteAcc, NoLock, Preserve)
@@ -19,11 +19,11 @@
FANR, 8,
Offset (0x58),
F1CR, 8
}
- Scope (_PR)
+ Scope (\_PR)
{
Processor (CPU0, 0x00, 0x00008010, 0x06) {}
}
Name (_S0, Package (0x02)
@@ -50,11 +50,11 @@
Method (_PIC, 1, NotSerialized)
{
Store (Arg0, PICF)
}
- Scope (_SB)
+ Scope (\_SB)
{
Name (OSTB, Ones)
Name (FWSO, "FWSO")
Name (ECEN, 0x00)
Name (ACST, 0x01)
@@ -838,10 +838,11 @@
{
Notify (VGA, 0x80)
Return (0x00)
}
}
+ Return (0x00)
}
Method (USTA, 0, NotSerialized)
{
If (LEqual (\_SB.PCI0.LPCB.Z000, 0x00))
@@ -3425,12 +3426,12 @@
" "
})
Name (PBST, Package (0x04)
{
0x00,
- Z00D,
- Z00D,
+ Z00C,
+ Z00C,
0x2710
})
Name (ERRC, 0x00)
Name (_PCL, Package (0x01)
{
@@ -3719,10 +3720,11 @@
}
}
}
Decrement (Local1)
+ Return (0x0)
}
}
Scope (\_TZ)
{
@@ -3829,13 +3831,14 @@
If (LEqual (Arg0, 0x05))
{
\_SB.PCI0.LPCB.PHSR (0x06, 0x00)
}
+ Return(Package(2){0, 0})
}
- Scope (_GPE)
+ Scope (\_GPE)
{
Method (_L17, 0, NotSerialized)
{
Notify (\_SB.LID, 0x80)
}
[-- Attachment #2: fix1705SMi.diff --]
[-- Type: text/x-diff, Size: 2279 bytes --]
--- dsdt.dsl 2004-10-25 22:11:22.501511136 +0100
+++ fixed.dsl 2004-10-25 22:11:03.349422696 +0100
@@ -1,10 +1,10 @@
/*
* Intel ACPI Component Architecture
- * AML Disassembler version 20040715
+ * AML Disassembler version 20030918
*
- * Disassembly of dsdt, Mon Oct 25 22:11:22 2004
+ * Disassembly of dsdt, Mon Aug 30 08:05:46 2004
*/
DefinitionBlock ("DSDT.aml", "DSDT", 1, "PTLTD ", "650M", 100925440)
{
OperationRegion (P80G, SystemIO, 0x80, 0x01)
Field (P80G, ByteAcc, NoLock, Preserve)
@@ -19,11 +19,11 @@
FANR, 8,
Offset (0x58),
F1CR, 8
}
- Scope (_PR)
+ Scope (\_PR)
{
Processor (CPU0, 0x00, 0x00008010, 0x06) {}
}
Name (_S0, Package (0x02)
@@ -50,11 +50,11 @@
Method (_PIC, 1, NotSerialized)
{
Store (Arg0, PICF)
}
- Scope (_SB)
+ Scope (\_SB)
{
Name (OSTB, Ones)
Name (FWSO, "FWSO")
Name (ECEN, 0x00)
Name (ACST, 0x01)
@@ -838,10 +838,11 @@
{
Notify (VGA, 0x80)
Return (0x00)
}
}
+ Return (0x00)
}
Method (USTA, 0, NotSerialized)
{
If (LEqual (\_SB.PCI0.LPCB.Z000, 0x00))
@@ -3425,12 +3426,12 @@
" "
})
Name (PBST, Package (0x04)
{
0x00,
- Z00D,
- Z00D,
+ Z00C,
+ Z00C,
0x2710
})
Name (ERRC, 0x00)
Name (_PCL, Package (0x01)
{
@@ -3719,10 +3720,11 @@
}
}
}
Decrement (Local1)
+ Return (0x0)
}
}
Scope (\_TZ)
{
@@ -3829,13 +3831,14 @@
If (LEqual (Arg0, 0x05))
{
\_SB.PCI0.LPCB.PHSR (0x06, 0x00)
}
+ Return(Package(2){0, 0})
}
- Scope (_GPE)
+ Scope (\_GPE)
{
Method (_L17, 0, NotSerialized)
{
Notify (\_SB.LID, 0x80)
}
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Acer Aspire 1705SMi LNKx?
[not found] ` <200410252247.39042.destynova-iUB+o6dfpG8i1yMB4YHZDQ@public.gmane.org>
@ 2004-10-26 11:54 ` Patrick Ale
[not found] ` <8d158e1f0410260454498849ac-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
0 siblings, 1 reply; 12+ messages in thread
From: Patrick Ale @ 2004-10-26 11:54 UTC (permalink / raw)
To: Oisín Mac Fhearaí
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f, Yu, Luming
Heya,
@@ -3829,13 +3831,14 @@
If (LEqual (Arg0, 0x05))
{
\_SB.PCI0.LPCB.PHSR (0x06, 0x00)
}
+ Return(Package(2){0, 0})
Does this actually work? When I try to compile it gives me an error
about an unexpected "("
Take care!
Patrick
On Mon, 25 Oct 2004 22:47:38 +0100, Oisín Mac Fhearaí
<destynova-iUB+o6dfpG8i1yMB4YHZDQ@public.gmane.org> wrote:
> On Monday 25 October 2004 16:52, Yu, Luming wrote:
> > It's nice to hear that you have fixed the buggy DSDT.
> > But I want to say MS windows should be ok with
> > the original DSDT, which breaks linux somehow.
> > To make sure linux can live with the original one,
> > I think we need to identify the quirks in the specific box, that
> > we can take into linux acpi for the sake of compatibility.
> > So, please give a brief description on what you did.
> >
> > Thanks
> > Luming
>
> The thing that worries me a little about this is, as time goes by and you
> create workarounds in the ACPI code (as, presumably, Windows has) for machine
> specific behaviour, will we end up with a constantly growing mess of code to
> handle them all, or will workarounds be phased out in favour of proper fixes?
>
> I've uploaded the original binary dsdt, disassembled version (which I did
> using quite an old version of iasl) and fixed version to
> http://www.redbrick.dcu.ie/~exolon/dsdt , /dsdt.dsl and /fixed.dsl
> respectively.
>
> Here is the -U5 diff for summary. The fixes I used were all standard except
> for the Z00D problem. I found no references to Z00D in any of the tables
> supplied by the machine, so using a fixed version uploaded to the dsdt
> repository, replaced them with Z00C. Robert Moore mentioned that these values
> may get overwritten anyway and 0 would also have worked, so I suppose it
> doesn't matter. :)
>
> good luck,
> Oisín
>
> ___
>
> --- dsdt.dsl 2004-10-25 22:11:22.501511136 +0100
> +++ fixed.dsl 2004-10-25 22:11:03.349422696 +0100
> @@ -1,10 +1,10 @@
> /*
> * Intel ACPI Component Architecture
> - * AML Disassembler version 20040715
> + * AML Disassembler version 20030918
> *
> - * Disassembly of dsdt, Mon Oct 25 22:11:22 2004
> + * Disassembly of dsdt, Mon Aug 30 08:05:46 2004
> */
> DefinitionBlock ("DSDT.aml", "DSDT", 1, "PTLTD ", "650M", 100925440)
> {
> OperationRegion (P80G, SystemIO, 0x80, 0x01)
> Field (P80G, ByteAcc, NoLock, Preserve)
> @@ -19,11 +19,11 @@
> FANR, 8,
> Offset (0x58),
> F1CR, 8
> }
>
> - Scope (_PR)
> + Scope (\_PR)
> {
> Processor (CPU0, 0x00, 0x00008010, 0x06) {}
> }
>
> Name (_S0, Package (0x02)
> @@ -50,11 +50,11 @@
> Method (_PIC, 1, NotSerialized)
> {
> Store (Arg0, PICF)
> }
>
> - Scope (_SB)
> + Scope (\_SB)
> {
> Name (OSTB, Ones)
> Name (FWSO, "FWSO")
> Name (ECEN, 0x00)
> Name (ACST, 0x01)
> @@ -838,10 +838,11 @@
> {
> Notify (VGA, 0x80)
> Return (0x00)
> }
> }
> + Return (0x00)
> }
>
> Method (USTA, 0, NotSerialized)
> {
> If (LEqual (\_SB.PCI0.LPCB.Z000, 0x00))
> @@ -3425,12 +3426,12 @@
> " "
> })
> Name (PBST, Package (0x04)
> {
> 0x00,
> - Z00D,
> - Z00D,
> + Z00C,
> + Z00C,
> 0x2710
> })
> Name (ERRC, 0x00)
> Name (_PCL, Package (0x01)
> {
> @@ -3719,10 +3720,11 @@
> }
> }
> }
>
> Decrement (Local1)
> + Return (0x0)
> }
> }
>
> Scope (\_TZ)
> {
> @@ -3829,13 +3831,14 @@
>
> If (LEqual (Arg0, 0x05))
> {
> \_SB.PCI0.LPCB.PHSR (0x06, 0x00)
> }
> + Return(Package(2){0, 0})
> }
>
> - Scope (_GPE)
> + Scope (\_GPE)
> {
> Method (_L17, 0, NotSerialized)
> {
> Notify (\_SB.LID, 0x80)
> }
>
>
>
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Acer Aspire 1705SMi LNKx?
[not found] ` <8d158e1f0410260454498849ac-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
@ 2004-10-26 18:46 ` Patrick Ale
[not found] ` <8d158e1f0410261146721481ed-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
0 siblings, 1 reply; 12+ messages in thread
From: Patrick Ale @ 2004-10-26 18:46 UTC (permalink / raw)
To: Oisín Mac Fhearaí
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f, Yu, Luming
Hello,
When I use the fixed.dsl you mentioned in your earlyer mail I dont get
the compile errors.
Unfortunately the error messages regarding the PCI0.LNK thingies still
appear for me.
But like I mentioned, I have an Aspire 1703 so maybe for me the
changes you made dont work quite as expected on an Aspire 1705 altho
the earlyer changes that were needed were the same as for me.
I apriciate your efford and time nevertheless. I'll just have to look
a bit further.
Thanks!
Patrick
On Tue, 26 Oct 2004 13:54:46 +0200, Patrick Ale <patrick.ale-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Heya,
>
> @@ -3829,13 +3831,14 @@
>
> If (LEqual (Arg0, 0x05))
> {
> \_SB.PCI0.LPCB.PHSR (0x06, 0x00)
> }
> + Return(Package(2){0, 0})
>
> Does this actually work? When I try to compile it gives me an error
> about an unexpected "("
>
> Take care!
>
> Patrick
>
> On Mon, 25 Oct 2004 22:47:38 +0100, Oisín Mac Fhearaí
>
>
> <destynova-iUB+o6dfpG8i1yMB4YHZDQ@public.gmane.org> wrote:
> > On Monday 25 October 2004 16:52, Yu, Luming wrote:
> > > It's nice to hear that you have fixed the buggy DSDT.
> > > But I want to say MS windows should be ok with
> > > the original DSDT, which breaks linux somehow.
> > > To make sure linux can live with the original one,
> > > I think we need to identify the quirks in the specific box, that
> > > we can take into linux acpi for the sake of compatibility.
> > > So, please give a brief description on what you did.
> > >
> > > Thanks
> > > Luming
> >
> > The thing that worries me a little about this is, as time goes by and you
> > create workarounds in the ACPI code (as, presumably, Windows has) for machine
> > specific behaviour, will we end up with a constantly growing mess of code to
> > handle them all, or will workarounds be phased out in favour of proper fixes?
> >
> > I've uploaded the original binary dsdt, disassembled version (which I did
> > using quite an old version of iasl) and fixed version to
> > http://www.redbrick.dcu.ie/~exolon/dsdt , /dsdt.dsl and /fixed.dsl
> > respectively.
> >
> > Here is the -U5 diff for summary. The fixes I used were all standard except
> > for the Z00D problem. I found no references to Z00D in any of the tables
> > supplied by the machine, so using a fixed version uploaded to the dsdt
> > repository, replaced them with Z00C. Robert Moore mentioned that these values
> > may get overwritten anyway and 0 would also have worked, so I suppose it
> > doesn't matter. :)
> >
> > good luck,
> > Oisín
> >
> > ___
> >
> > --- dsdt.dsl 2004-10-25 22:11:22.501511136 +0100
> > +++ fixed.dsl 2004-10-25 22:11:03.349422696 +0100
> > @@ -1,10 +1,10 @@
> > /*
> > * Intel ACPI Component Architecture
> > - * AML Disassembler version 20040715
> > + * AML Disassembler version 20030918
> > *
> > - * Disassembly of dsdt, Mon Oct 25 22:11:22 2004
> > + * Disassembly of dsdt, Mon Aug 30 08:05:46 2004
> > */
> > DefinitionBlock ("DSDT.aml", "DSDT", 1, "PTLTD ", "650M", 100925440)
> > {
> > OperationRegion (P80G, SystemIO, 0x80, 0x01)
> > Field (P80G, ByteAcc, NoLock, Preserve)
> > @@ -19,11 +19,11 @@
> > FANR, 8,
> > Offset (0x58),
> > F1CR, 8
> > }
> >
> > - Scope (_PR)
> > + Scope (\_PR)
> > {
> > Processor (CPU0, 0x00, 0x00008010, 0x06) {}
> > }
> >
> > Name (_S0, Package (0x02)
> > @@ -50,11 +50,11 @@
> > Method (_PIC, 1, NotSerialized)
> > {
> > Store (Arg0, PICF)
> > }
> >
> > - Scope (_SB)
> > + Scope (\_SB)
> > {
> > Name (OSTB, Ones)
> > Name (FWSO, "FWSO")
> > Name (ECEN, 0x00)
> > Name (ACST, 0x01)
> > @@ -838,10 +838,11 @@
> > {
> > Notify (VGA, 0x80)
> > Return (0x00)
> > }
> > }
> > + Return (0x00)
> > }
> >
> > Method (USTA, 0, NotSerialized)
> > {
> > If (LEqual (\_SB.PCI0.LPCB.Z000, 0x00))
> > @@ -3425,12 +3426,12 @@
> > " "
> > })
> > Name (PBST, Package (0x04)
> > {
> > 0x00,
> > - Z00D,
> > - Z00D,
> > + Z00C,
> > + Z00C,
> > 0x2710
> > })
> > Name (ERRC, 0x00)
> > Name (_PCL, Package (0x01)
> > {
> > @@ -3719,10 +3720,11 @@
> > }
> > }
> > }
> >
> > Decrement (Local1)
> > + Return (0x0)
> > }
> > }
> >
> > Scope (\_TZ)
> > {
> > @@ -3829,13 +3831,14 @@
> >
> > If (LEqual (Arg0, 0x05))
> > {
> > \_SB.PCI0.LPCB.PHSR (0x06, 0x00)
> > }
> > + Return(Package(2){0, 0})
> > }
> >
> > - Scope (_GPE)
> > + Scope (\_GPE)
> > {
> > Method (_L17, 0, NotSerialized)
> > {
> > Notify (\_SB.LID, 0x80)
> > }
> >
> >
> >
>
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id\x12065&op=click
^ permalink raw reply [flat|nested] 12+ messages in thread
* RE: Acer Aspire 1705SMi LNKx?
@ 2004-10-27 1:35 Yu, Luming
0 siblings, 0 replies; 12+ messages in thread
From: Yu, Luming @ 2004-10-27 1:35 UTC (permalink / raw)
To: Patrick Ale, Oisín Mac Fhearaí
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f
_CRS for the device should return IRQ descriptor .
The first byte should be : Value = 0010001nB (Type = 0, small item name = 0x4, length = (2 or 3))
Thanks
Luming
>-----Original Message-----
>From: Patrick Ale [mailto:patrick.ale-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org]
>Sent: 2004年10月27日 2:46
>To: Oisín Mac Fhearaí
>Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org; Yu, Luming
>Subject: Re: [ACPI] Acer Aspire 1705SMi LNKx?
>
>Hello,
>
>When I use the fixed.dsl you mentioned in your earlyer mail I dont get
>the compile errors.
>Unfortunately the error messages regarding the PCI0.LNK thingies still
>appear for me.
>But like I mentioned, I have an Aspire 1703 so maybe for me the
>changes you made dont work quite as expected on an Aspire 1705 altho
>the earlyer changes that were needed were the same as for me.
>
>I apriciate your efford and time nevertheless. I'll just have to look
>a bit further.
>
>Thanks!
>
>Patrick
>
>
>On Tue, 26 Oct 2004 13:54:46 +0200, Patrick Ale
><patrick.ale-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>> Heya,
>>
>> @@ -3829,13 +3831,14 @@
>>
>> If (LEqual (Arg0, 0x05))
>> {
>> \_SB.PCI0.LPCB.PHSR (0x06, 0x00)
>> }
>> + Return(Package(2){0, 0})
>>
>> Does this actually work? When I try to compile it gives me an error
>> about an unexpected "("
>>
>> Take care!
>>
>> Patrick
>>
>> On Mon, 25 Oct 2004 22:47:38 +0100, Oisín Mac Fhearaí
>>
>>
>> <destynova-iUB+o6dfpG8i1yMB4YHZDQ@public.gmane.org> wrote:
>> > On Monday 25 October 2004 16:52, Yu, Luming wrote:
>> > > It's nice to hear that you have fixed the buggy DSDT.
>> > > But I want to say MS windows should be ok with
>> > > the original DSDT, which breaks linux somehow.
>> > > To make sure linux can live with the original one,
>> > > I think we need to identify the quirks in the specific box, that
>> > > we can take into linux acpi for the sake of compatibility.
>> > > So, please give a brief description on what you did.
>> > >
>> > > Thanks
>> > > Luming
>> >
>> > The thing that worries me a little about this is, as time
>goes by and you
>> > create workarounds in the ACPI code (as, presumably,
>Windows has) for machine
>> > specific behaviour, will we end up with a constantly
>growing mess of code to
>> > handle them all, or will workarounds be phased out in
>favour of proper fixes?
>> >
>> > I've uploaded the original binary dsdt, disassembled
>version (which I did
>> > using quite an old version of iasl) and fixed version to
>> > http://www.redbrick.dcu.ie/~exolon/dsdt , /dsdt.dsl and /fixed.dsl
>> > respectively.
>> >
>> > Here is the -U5 diff for summary. The fixes I used were
>all standard except
>> > for the Z00D problem. I found no references to Z00D in any
>of the tables
>> > supplied by the machine, so using a fixed version uploaded
>to the dsdt
>> > repository, replaced them with Z00C. Robert Moore
>mentioned that these values
>> > may get overwritten anyway and 0 would also have worked,
>so I suppose it
>> > doesn't matter. :)
>> >
>> > good luck,
>> > Oisín
>> >
>> > ___
>> >
>> > --- dsdt.dsl 2004-10-25 22:11:22.501511136 +0100
>> > +++ fixed.dsl 2004-10-25 22:11:03.349422696 +0100
>> > @@ -1,10 +1,10 @@
>> > /*
>> > * Intel ACPI Component Architecture
>> > - * AML Disassembler version 20040715
>> > + * AML Disassembler version 20030918
>> > *
>> > - * Disassembly of dsdt, Mon Oct 25 22:11:22 2004
>> > + * Disassembly of dsdt, Mon Aug 30 08:05:46 2004
>> > */
>> > DefinitionBlock ("DSDT.aml", "DSDT", 1, "PTLTD ", "650M",
>100925440)
>> > {
>> > OperationRegion (P80G, SystemIO, 0x80, 0x01)
>> > Field (P80G, ByteAcc, NoLock, Preserve)
>> > @@ -19,11 +19,11 @@
>> > FANR, 8,
>> > Offset (0x58),
>> > F1CR, 8
>> > }
>> >
>> > - Scope (_PR)
>> > + Scope (\_PR)
>> > {
>> > Processor (CPU0, 0x00, 0x00008010, 0x06) {}
>> > }
>> >
>> > Name (_S0, Package (0x02)
>> > @@ -50,11 +50,11 @@
>> > Method (_PIC, 1, NotSerialized)
>> > {
>> > Store (Arg0, PICF)
>> > }
>> >
>> > - Scope (_SB)
>> > + Scope (\_SB)
>> > {
>> > Name (OSTB, Ones)
>> > Name (FWSO, "FWSO")
>> > Name (ECEN, 0x00)
>> > Name (ACST, 0x01)
>> > @@ -838,10 +838,11 @@
>> > {
>> > Notify (VGA, 0x80)
>> > Return (0x00)
>> > }
>> > }
>> > + Return (0x00)
>> > }
>> >
>> > Method (USTA, 0, NotSerialized)
>> > {
>> > If (LEqual (\_SB.PCI0.LPCB.Z000, 0x00))
>> > @@ -3425,12 +3426,12 @@
>> > " "
>> > })
>> > Name (PBST, Package (0x04)
>> > {
>> > 0x00,
>> > - Z00D,
>> > - Z00D,
>> > + Z00C,
>> > + Z00C,
>> > 0x2710
>> > })
>> > Name (ERRC, 0x00)
>> > Name (_PCL, Package (0x01)
>> > {
>> > @@ -3719,10 +3720,11 @@
>> > }
>> > }
>> > }
>> >
>> > Decrement (Local1)
>> > + Return (0x0)
>> > }
>> > }
>> >
>> > Scope (\_TZ)
>> > {
>> > @@ -3829,13 +3831,14 @@
>> >
>> > If (LEqual (Arg0, 0x05))
>> > {
>> > \_SB.PCI0.LPCB.PHSR (0x06, 0x00)
>> > }
>> > + Return(Package(2){0, 0})
>> > }
>> >
>> > - Scope (_GPE)
>> > + Scope (\_GPE)
>> > {
>> > Method (_L17, 0, NotSerialized)
>> > {
>> > Notify (\_SB.LID, 0x80)
>> > }
>> >
>> >
>> >
>>
>
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id\x12065&op=click
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Acer Aspire 1705SMi LNKx?
[not found] ` <8d158e1f0410261146721481ed-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
@ 2004-10-27 5:31 ` Oisín Mac Fhearaí
0 siblings, 0 replies; 12+ messages in thread
From: Oisín Mac Fhearaí @ 2004-10-27 5:31 UTC (permalink / raw)
To: Patrick Ale; +Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f, Yu, Luming
No, I still get the LNKx errors while booting. I don't know what it means,
TBH.
The only things that bother me really about the machine's compatibility with
linux's current implementation of ACPI is that waking from S4 doesn't
power-on the screen, although the system seems responsive to commands... and
waking from S5 (?) works, but more often than not causes my orinoco wireless
card to stop working properly.
Also still can't sleep in X, thanks to poxy nvidia.
Oisín
On Tuesday 26 October 2004 19:46, Patrick Ale wrote:
...
> Unfortunately the error messages regarding the PCI0.LNK thingies still
> appear for me.
> But like I mentioned, I have an Aspire 1703 so maybe for me the
> changes you made dont work quite as expected on an Aspire 1705 altho
> the earlyer changes that were needed were the same as for me.
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
^ permalink raw reply [flat|nested] 12+ messages in thread
* RE: Acer Aspire 1705SMi LNKx?
@ 2004-10-27 5:36 Yu, Luming
0 siblings, 0 replies; 12+ messages in thread
From: Yu, Luming @ 2004-10-27 5:36 UTC (permalink / raw)
To: Oisín Mac Fhearaí, Patrick Ale
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f
Would you please file a bug on bugzilla.kernel.org for
better tracking this problem.
Thanks
Luming
>-----Original Message-----
>From: Oisín Mac Fhearaí [mailto:destynova-iUB+o6dfpG8i1yMB4YHZDQ@public.gmane.org]
>Sent: 2004年10月27日 13:31
>To: Patrick Ale
>Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org; Yu, Luming
>Subject: Re: [ACPI] Acer Aspire 1705SMi LNKx?
>
>No, I still get the LNKx errors while booting. I don't know
>what it means,
>TBH.
>
>The only things that bother me really about the machine's
>compatibility with
>linux's current implementation of ACPI is that waking from S4 doesn't
>power-on the screen, although the system seems responsive to
>commands... and
>waking from S5 (?) works, but more often than not causes my
>orinoco wireless
>card to stop working properly.
>Also still can't sleep in X, thanks to poxy nvidia.
>
>Oisín
>
>On Tuesday 26 October 2004 19:46, Patrick Ale wrote:
>...
>> Unfortunately the error messages regarding the PCI0.LNK
>thingies still
>> appear for me.
>> But like I mentioned, I have an Aspire 1703 so maybe for me the
>> changes you made dont work quite as expected on an Aspire 1705 altho
>> the earlyer changes that were needed were the same as for me.
>
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id\x12065&op=click
^ permalink raw reply [flat|nested] 12+ messages in thread
* RE: Acer Aspire 1705SMi LNKx?
@ 2004-10-27 21:54 Moore, Robert
0 siblings, 0 replies; 12+ messages in thread
From: Moore, Robert @ 2004-10-27 21:54 UTC (permalink / raw)
To: Oisín Mac Fhearaí,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f
Cc: Yu, Luming
> The thing that worries me a little about this is, as time goes by and you
> create workarounds in the ACPI code (as, presumably, Windows has) for
> machine
> specific behaviour, will we end up with a constantly growing mess of code
> to
> handle them all, or will workarounds be phased out in favour of proper
> fixes?
>
A growing mess of code :(
Fortunately, most of the 'workarounds' are small and contained.
Bob
> -----Original Message-----
> From: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org [mailto:acpi-devel-
> admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf Of Oisín Mac Fhearaí
> Sent: Monday, October 25, 2004 2:48 PM
> To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> Cc: Yu, Luming
> Subject: Re: [ACPI] Acer Aspire 1705SMi LNKx?
>
> On Monday 25 October 2004 16:52, Yu, Luming wrote:
> > It's nice to hear that you have fixed the buggy DSDT.
> > But I want to say MS windows should be ok with
> > the original DSDT, which breaks linux somehow.
> > To make sure linux can live with the original one,
> > I think we need to identify the quirks in the specific box, that
> > we can take into linux acpi for the sake of compatibility.
> > So, please give a brief description on what you did.
> >
> > Thanks
> > Luming
>
> The thing that worries me a little about this is, as time goes by and you
> create workarounds in the ACPI code (as, presumably, Windows has) for
> machine
> specific behaviour, will we end up with a constantly growing mess of code
> to
> handle them all, or will workarounds be phased out in favour of proper
> fixes?
>
> I've uploaded the original binary dsdt, disassembled version (which I did
> using quite an old version of iasl) and fixed version to
> http://www.redbrick.dcu.ie/~exolon/dsdt , /dsdt.dsl and /fixed.dsl
> respectively.
>
> Here is the -U5 diff for summary. The fixes I used were all standard
> except
> for the Z00D problem. I found no references to Z00D in any of the tables
> supplied by the machine, so using a fixed version uploaded to the dsdt
> repository, replaced them with Z00C. Robert Moore mentioned that these
> values
> may get overwritten anyway and 0 would also have worked, so I suppose it
> doesn't matter. :)
>
> good luck,
> Oisín
>
> ___
>
> --- dsdt.dsl 2004-10-25 22:11:22.501511136 +0100
> +++ fixed.dsl 2004-10-25 22:11:03.349422696 +0100
> @@ -1,10 +1,10 @@
> /*
> * Intel ACPI Component Architecture
> - * AML Disassembler version 20040715
> + * AML Disassembler version 20030918
> *
> - * Disassembly of dsdt, Mon Oct 25 22:11:22 2004
> + * Disassembly of dsdt, Mon Aug 30 08:05:46 2004
> */
> DefinitionBlock ("DSDT.aml", "DSDT", 1, "PTLTD ", "650M", 100925440)
> {
> OperationRegion (P80G, SystemIO, 0x80, 0x01)
> Field (P80G, ByteAcc, NoLock, Preserve)
> @@ -19,11 +19,11 @@
> FANR, 8,
> Offset (0x58),
> F1CR, 8
> }
>
> - Scope (_PR)
> + Scope (\_PR)
> {
> Processor (CPU0, 0x00, 0x00008010, 0x06) {}
> }
>
> Name (_S0, Package (0x02)
> @@ -50,11 +50,11 @@
> Method (_PIC, 1, NotSerialized)
> {
> Store (Arg0, PICF)
> }
>
> - Scope (_SB)
> + Scope (\_SB)
> {
> Name (OSTB, Ones)
> Name (FWSO, "FWSO")
> Name (ECEN, 0x00)
> Name (ACST, 0x01)
> @@ -838,10 +838,11 @@
> {
> Notify (VGA, 0x80)
> Return (0x00)
> }
> }
> + Return (0x00)
> }
>
> Method (USTA, 0, NotSerialized)
> {
> If (LEqual (\_SB.PCI0.LPCB.Z000, 0x00))
> @@ -3425,12 +3426,12 @@
> " "
> })
> Name (PBST, Package (0x04)
> {
> 0x00,
> - Z00D,
> - Z00D,
> + Z00C,
> + Z00C,
> 0x2710
> })
> Name (ERRC, 0x00)
> Name (_PCL, Package (0x01)
> {
> @@ -3719,10 +3720,11 @@
> }
> }
> }
>
> Decrement (Local1)
> + Return (0x0)
> }
> }
>
> Scope (\_TZ)
> {
> @@ -3829,13 +3831,14 @@
>
> If (LEqual (Arg0, 0x05))
> {
> \_SB.PCI0.LPCB.PHSR (0x06, 0x00)
> }
> + Return(Package(2){0, 0})
> }
>
> - Scope (_GPE)
> + Scope (\_GPE)
> {
> Method (_L17, 0, NotSerialized)
> {
> Notify (\_SB.LID, 0x80)
> }
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id\x12065&op=click
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2004-10-27 21:54 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-10-25 15:52 Acer Aspire 1705SMi LNKx? Yu, Luming
2004-10-25 19:10 ` Patrick Ale
[not found] ` <8d158e1f04102512101b5808e2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2004-10-25 19:18 ` Patrick Ale
2004-10-25 21:47 ` Oisín Mac Fhearaí
[not found] ` <200410252247.39042.destynova-iUB+o6dfpG8i1yMB4YHZDQ@public.gmane.org>
2004-10-26 11:54 ` Patrick Ale
[not found] ` <8d158e1f0410260454498849ac-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2004-10-26 18:46 ` Patrick Ale
[not found] ` <8d158e1f0410261146721481ed-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2004-10-27 5:31 ` Oisín Mac Fhearaí
-- strict thread matches above, loose matches on Subject: below --
2004-10-27 21:54 Moore, Robert
2004-10-27 5:36 Yu, Luming
2004-10-27 1:35 Yu, Luming
2004-10-25 8:09 Oisín Mac Fhearaí
[not found] ` <200410250909.41761.destynova-iUB+o6dfpG8i1yMB4YHZDQ@public.gmane.org>
2004-10-25 14:30 ` Patrick Ale
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox