Mark Santcroos wrote:
On Mon, Aug 26, 2002 at 03:01:48AM +0900, Mitsuru IWASAKI wrote:
>How about this one?
>http://people.freebsd.org/~iwasaki/acpi/vga_pci-20020228.tar.gz
>
>This simply set PCI_POWERSTATE_D0 for VGA device on wakeup.
This didn't work unfortunately.
The problem is actually a
On Sun, Aug 25, 2002 at 06:59:45PM +0200, Mark Santcroos wrote:
> I have a Dell Latitude C640 and my screen won't come back after a suspend.
> The machine works fine besides that.
FYI:
I just did a minimal Linux installation on this machine and tried latest
kernel with latest ACPI. Exactly the
On Wed, 28 Aug 2002, Mitsuru IWASAKI wrote:
> > 1) Fix the ASL so that it compiles without errors or warnings
> > 2) Override the BIOS version of the table with your new one. (I don't know
> > how this is done on FreeBSD, someone else will have to help you.
>
> Attached patches will fix the ASL
: Wednesday, August 28, 2002 3:36 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: [acpi-jp 1759] Re: Call for testers: acpica-unix-20020815
> 1) Fix the ASL so that it compiles without errors or warnings
> 2) Override the BIOS version of the table with your new on
>Thanks a lot. I must apologize though, I had the same error with
>previous versions of acpi (I should have checked, sorry, I confounded
>2 laptops)
This is very important fact for me! OK, I'll import 20020815 version
today.
BTW, Could you check your BIOS setting and see if printer
> 1) Fix the ASL so that it compiles without errors or warnings
> 2) Override the BIOS version of the table with your new one. (I don't know
> how this is done on FreeBSD, someone else will have to help you.
Attached patches will fix the ASL.
For compiling and overriding, please refer to acpi(4)
Thus spake Terry Lambert <[EMAIL PROTECTED]>:
> > Sometimes. But see http://www.tuxedo.org/~esr/jargon/html/entry/DWIM.html
>
> I understand, but having a different failure is no worse than
> having a failure, I think. In either case, it doesn't work,
> even if it doesn't work in an entirely di
David Schultz wrote:
> > So the worst possible outcome in the failure case is that it
> > fails -- which it already does, without the assumption -- and
> > the best possible outcome is that it succeeds when it wouldn't
> > have.
> >
> > "Anything that works is better than anything that doesn't"
>
Thus spake Terry Lambert <[EMAIL PROTECTED]>:
> FWIW, there's historical precedent for this: the DEC VAX/VMS
> C compiler would imply semicolons for the programmer that
> forgot them, and a couple of other similar "fixups", issue a
> warning, but the resulting code would run "as the programmer
> m
Hi,
> This looks like the (in)famous "implicit return" problem that is in some
> Toshiba ASL files.
>
> Method(_CRS) {
> CRS_(0x10)
> }
No, this is not "implicit return" problem. We have a workaround in
ACPI CA code in FreeBSD locally, and it
--Original Message-
> From: Yann Berthier [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, August 27, 2002 3:19 PM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: [acpi-jp 1750] Re: Call for testers: acpica-unix-20020815
>
> On Tue, 27 Aug 2002, Moore, Robert wrote:
>
Sent: Tuesday, August 27, 2002 3:19 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: [acpi-jp 1750] Re: Call for testers: acpica-unix-20020815
On Tue, 27 Aug 2002, Moore, Robert wrote:
>
> This looks like the (in)famous "implicit return" problem that is in som
: Tuesday, August 27, 2002 3:40 PM
To: Moore, Robert
Cc: 'Mitsuru IWASAKI'; [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]; Grover, Andrew
Subject: Re: [acpi-jp 1735] Re: Call for testers: acpica-unix-20020815
"Moore, Robert" wrote:
> I think you are missing somethin
"Moore, Robert" wrote:
> I think you are missing something:
>
> 1) BIOS vendor writes ASL
> 2) BIOS vendor compiles ASL to AML byte-code
> 3) BIOS vendor puts AML into BIOS
> 4) OS gets AML from the BIOS
> 5) OS interprets AML
>
> The error you are experiencing is in (5). There is no return sta
On Tue, 27 Aug 2002, Moore, Robert wrote:
>
> This looks like the (in)famous "implicit return" problem that is in some
> Toshiba ASL files.
>
> Method(_CRS) {
> CRS_(0x10)
> }
>
> This does NOT actually return a value and the ASL code is inco
, Andrew
Subject: Re: [acpi-jp 1735] Re: Call for testers: acpica-unix-20020815
"Moore, Robert" wrote:
> Well, the *real* problem is that there is no Return AML opcode in the
> control method and the interpreter therefore does not return a value.
>
> However, to answer your ques
"Moore, Robert" wrote:
> Well, the *real* problem is that there is no Return AML opcode in the
> control method and the interpreter therefore does not return a value.
>
> However, to answer your question with a question:
>
> Would you ask a C compiler, or any other compiler for that matter, to
>
Re: [acpi-jp 1735] Re: Call for testers: acpica-unix-20020815
"Moore, Robert" wrote:
> This looks like the (in)famous "implicit return" problem that is in some
> Toshiba ASL files.
>
> Method(_CRS) {
> CRS_(0x10)
>
"Moore, Robert" wrote:
> This looks like the (in)famous "implicit return" problem that is in some
> Toshiba ASL files.
>
> Method(_CRS) {
> CRS_(0x10)
> }
>
> This does NOT actually return a value and the ASL code is incorrect. It has
> to be:
On Tue, 27 Aug 2002, Mitsuru IWASAKI wrote:
> Hi,
>
> Could you put the following lines into /boot/loader.conf and send
> dmesg output again?
>
> debug.acpi.layer="ACPI_ALL_COMPONENTS"
> debug.acpi.level="ACPI_LV_ERROR"
>
Of course, here we go :)
> >[sent privately to not spam
PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: Re: [acpi-jp 1735] Re: Call for testers: acpica-unix-20020815
Hi,
Could you put the following lines into /boot/loader.conf and send
dmesg output again?
debug.acpi.layer="ACPI_ALL_COMPONENTS"
debug.acpi.
Hi,
Could you put the following lines into /boot/loader.conf and send
dmesg output again?
debug.acpi.layer="ACPI_ALL_COMPONENTS"
debug.acpi.level="ACPI_LV_ERROR"
>[sent privately to not spam the lists with my dump files]
>
> On Mon, 26 Aug 2002, Mitsuru IWASAKI wrote:
>
> > >
Hi,
> On Mon, Aug 26, 2002 at 10:32:58PM +0900, Mitsuru IWASAKI wrote:
> > Any volunteers to solve this problem?
>
> Well yes, me.
>
> Like I said, I don't have experience with ACPI yet, but basicly I need to
> get this working so that makes me a good candidate ;)
Thanks, very cool!
> Am I co
On Mon, Aug 26, 2002 at 10:32:58PM +0900, Mitsuru IWASAKI wrote:
> Any volunteers to solve this problem?
Well yes, me.
Like I said, I don't have experience with ACPI yet, but basicly I need to
get this working so that makes me a good candidate ;)
I just registered myself as a developer on ati.c
> One other note:
>
> At boot time the VGA is reported as:
> Aug 25 21:15:20 laptop kernel: vga0: at port 0x3c0-0x3df iomem
>0xa-0xb on isa0
>
> And when I load your module:
> Aug 25 21:12:44 laptop kernel: vga_pci0: port 0xc000-0xc0ff mem
>0xfcff-0xfcff,0xe000-0xe7f
>FYI, I have now a "can't fetch resources for \\_SB_.PCI0.FNC0.PRT_ -
>AE_BAD_DATA" with acpica-unix-20020815 during boot.
I'd like to make sure if AE_BAD_DATA error occurred w/ previous
versions (acpica-unix-20020725, 20020611, 20020404...) ?
Or first time w/ acpica-unix-20020815 ?
Anyw
Mark Santcroos wrote:
> The problem is actually a bit weird. When I suspend (close the lid or with
> the key combo) the display is not turned off actually. It does go in some
> form of suspend however. When I resume, the machine comes back to life
> again, but the screen goes off at that moment.
Hello,
I applied the patch, and nothing changed, so it works :)
What tools do you use to check battery state? Any links on userland
tools for monitoring / controling the ACPI (other than acpiconf) ?
On my laptop, power switch, lid switch and stuff like that show up under
boot-up, but they d
On Mon, Aug 26, 2002 at 03:01:48AM +0900, Mitsuru IWASAKI wrote:
> How about this one?
> http://people.freebsd.org/~iwasaki/acpi/vga_pci-20020228.tar.gz
>
> This simply set PCI_POWERSTATE_D0 for VGA device on wakeup.
This didn't work unfortunately.
The problem is actually a bit weird. When I su
On Mon, 26 Aug 2002, Mitsuru IWASAKI wrote:
> > > > I have a Dell Latitude C640 and my screen won't come back after a suspend.
> > > > The machine works fine besides that.
> > >
> > > OK, I think this is not related with ACPI CA code update.
> >
> > If that was not clear, it also didn't work be
> iwasaki> Index: isa/syscons_isa.c
> iwasaki> ===
> iwasaki> RCS file: /home/ncvs/src/sys/isa/syscons_isa.c,v
> iwasaki> retrieving revision 1.17
> iwasaki> diff -u -r1.17 syscons_isa.c
> iwasaki> --- isa/syscons_isa.c30 Jun
Hi,
>>> Mon, 26 Aug 2002 02:37:36 +0900 (JST),
>>> Mitsuru IWASAKI <[EMAIL PROTECTED]> said:
iwasaki> If you have this problem w/ X running, and don't have w/o X,
iwasaki> please try attached patches.
iwasaki> Index: isa/syscons_isa.c
iwasaki> ===
> > > I have a Dell Latitude C640 and my screen won't come back after a suspend.
> > > The machine works fine besides that.
> >
> > OK, I think this is not related with ACPI CA code update.
>
> If that was not clear, it also didn't work before.
understood. I meant that ACPI CA code changes won
On Mon, Aug 26, 2002 at 02:37:36AM +0900, Mitsuru IWASAKI wrote:
> > I applied the patches, and I still have the same results on my laptop.
> >
> > I have a Dell Latitude C640 and my screen won't come back after a suspend.
> > The machine works fine besides that.
>
> OK, I think this is not rela
> I applied the patches, and I still have the same results on my laptop.
>
> I have a Dell Latitude C640 and my screen won't come back after a suspend.
> The machine works fine besides that.
OK, I think this is not related with ACPI CA code update.
Our device driver (maybe syscons?) or X server
Hi Mitsuru,
I applied the patches, and I still have the same results on my laptop.
I have a Dell Latitude C640 and my screen won't come back after a suspend.
The machine works fine besides that.
Do you have any idea/advice how this can be debugged?
Thanks
Mark
On Thu, Aug 22, 2002 at 11:51:
I'm going to import Intel acpica-unix-20020815 sometime early next
week. Please test new version of acpica and give feedback before my
importing.
Major fix in this version is Ref/Deref operators bug fix.
Personally I'm very happy with the new version because
now my laptop (FIVA 206VL) reports cor
37 matches
Mail list logo
