Re: ACPI problems with Compaq Evo N610c
On Wed, 30 Jul 2003, Cagle, John (ISS-Houston) wrote: I have a feeling that my acpi table didn't actually get overridden though, due to the following from dmesg: ACPI: DSDT was overridden. -0424: *** Error: UtAllocate: Could not allocate size 6e49202a ACPI-0428: *** Error: Could not allocate table memory for [/* ] length 6e49202a ACPI-0368: *** Error: Could not copy override ACPI table, AE_NO_MEMORY This looks like an unterminated comment character (/*). I see another person's ASL fixed this for you though. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: ACPI problems with Compaq Evo N610c (fwd)
Hello Doug, From [EMAIL PROTECTED] Fri Sep 5 05:49:49 2003 Not sure if you got a copy of this first time or not... Sorry, no I did not. My mail pickup system got screwed several times lately. -- Forwarded message -- From: Doug Barton [EMAIL PROTECTED] To: Cagle, John (ISS-Houston) [EMAIL PROTECTED] Cc: Tony Maher [EMAIL PROTECTED], Robert Blacquière [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Date: Sun, 31 Aug 2003 19:50:03 -0700 (PDT) Organization: http://www.FreeBSD.org/ Subject: RE: ACPI problems with Compaq Evo N610c I got interested in this recently because I inherited one of these laptops from work. On Wed, 30 Jul 2003, Cagle, John (ISS-Houston) wrote: Which version of the N610C BIOS are you using? (F.14 is the latest on the hp.com website.) I know that the _OSI(Windows 2001) bug will be fixed in the F.15 release, but I don't think the _GL_ portion of your patch will be included. Did you have to remove the Acquire Release of _GL_ in order to get xbat to work? (This is not a problem we see with Linux ACPI in 2.4.21, so I think that FreeBSD's ACPI stack needs updating.) I just updated to F.15, and it does indeed fix the windows bit in the output of 'acpidump -d'. However, even with Tony's recommendation of removing the acquire/release of _GL in methods C12C and C12D, I still can't get xbatt or wmbattery to run, even with the very latest -current (which has had at least one acpi stack upgrade since 7/30). When I run either command, it locks the box tight. If I ever get a cursor back, I have to Ctrl-Alt-Backspace to get out of X, since I can't actually type anything. I have a feeling that my acpi table didn't actually get overridden though, due to the following from dmesg: ACPI: DSDT was overridden. -0424: *** Error: UtAllocate: Could not allocate size 6e49202a ACPI-0428: *** Error: Could not allocate table memory for [/* ] length 6e49202a ACPI-0368: *** Error: Could not copy override ACPI table, AE_NO_MEMORY This certainly seems to be the case. I see ACPI: DSDT was overridden. ACPI-0375: *** Info: Table [DSDT] replaced by host OS Also, the before and after acpidump's don't show anything different. So, I'm curious if wmbatt is still working for Tony and Robert or not with the latest -current. I am currently running FreeBSD k9.home 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sat Aug 30 11:48:23 EST 2003 [EMAIL PROTECTED]:/var/obj/space/usr/src/sys/K9 i386 and xbatt works (to certain extent - it show s being power cable in and out and shos charging state when first booted up but after insertion/removal of power cord it no longer shows charging stae or time left in battery) If I get a cahnce on weekend I'll update to latest and let you know. The other problem I'm having is that doing 'sysctl -a', or just 'sysctl hw.acpi' locks the system tight for a couple minutes, and never completes. The last line that's printed to the screen is: hw.acpi.thermal.tz1._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 Any ideas on that one? This is becase the DSDT was not overridden. I used to see this as well. -- tonym ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: ACPI problems with Compaq Evo N610c
I got interested in this recently because I inherited one of these laptops from work. On Wed, 30 Jul 2003, Cagle, John (ISS-Houston) wrote: Which version of the N610C BIOS are you using? (F.14 is the latest on the hp.com website.) I know that the _OSI(Windows 2001) bug will be fixed in the F.15 release, but I don't think the _GL_ portion of your patch will be included. Did you have to remove the Acquire Release of _GL_ in order to get xbat to work? (This is not a problem we see with Linux ACPI in 2.4.21, so I think that FreeBSD's ACPI stack needs updating.) I just updated to F.15, and it does indeed fix the windows bit in the output of 'acpidump -d'. However, even with Tony's recommendation of removing the acquire/release of _GL in methods C12C and C12D, I still can't get xbatt or wmbattery to run, even with the very latest -current (which has had at least one acpi stack upgrade since 7/30). When I run either command, it locks the box tight. If I ever get a cursor back, I have to Ctrl-Alt-Backspace to get out of X, since I can't actually type anything. I have a feeling that my acpi table didn't actually get overridden though, due to the following from dmesg: ACPI: DSDT was overridden. -0424: *** Error: UtAllocate: Could not allocate size 6e49202a ACPI-0428: *** Error: Could not allocate table memory for [/* ] length 6e49202a ACPI-0368: *** Error: Could not copy override ACPI table, AE_NO_MEMORY Also, the before and after acpidump's don't show anything different. So, I'm curious if wmbatt is still working for Tony and Robert or not with the latest -current. The other problem I'm having is that doing 'sysctl -a', or just 'sysctl hw.acpi' locks the system tight for a couple minutes, and never completes. The last line that's printed to the screen is: hw.acpi.thermal.tz1._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 Any ideas on that one? Thanks, Doug /boot/loader.conf is now hw.pci.allow_unsupported_io_range=1 acpi_dsdt_load=YES acpi_dsdt_name=/boot/acpi_dsdt.aml -- This .signature sanitized for your protection ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI problems with Compaq Evo N610c
I don't seem to have these problems. I use xbattbar without problem. I use this acpi_dsdt code: http://www.guldan.cistron.nl/acpi_dsdt.dsl On Sun, Aug 31, 2003 at 07:50:03PM -0700, Doug Barton wrote: I got interested in this recently because I inherited one of these laptops from work. On Wed, 30 Jul 2003, Cagle, John (ISS-Houston) wrote: I just updated to F.15, and it does indeed fix the windows bit in the output of 'acpidump -d'. However, even with Tony's recommendation of removing the acquire/release of _GL in methods C12C and C12D, I still can't get xbatt or wmbattery to run, even with the very latest -current (which has had at least one acpi stack upgrade since 7/30). When I run either command, it locks the box tight. If I ever get a cursor back, I have to Ctrl-Alt-Backspace to get out of X, since I can't actually type anything. I have a feeling that my acpi table didn't actually get overridden though, due to the following from dmesg: ACPI: DSDT was overridden. -0424: *** Error: UtAllocate: Could not allocate size 6e49202a ACPI-0428: *** Error: Could not allocate table memory for [/* ] length 6e49202a ACPI-0368: *** Error: Could not copy override ACPI table, AE_NO_MEMORY Also, the before and after acpidump's don't show anything different. So, I'm curious if wmbatt is still working for Tony and Robert or not with the latest -current. The other problem I'm having is that doing 'sysctl -a', or just 'sysctl hw.acpi' locks the system tight for a couple minutes, and never completes. The last line that's printed to the screen is: hw.acpi.thermal.tz1._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 Any ideas on that one? Thanks, Doug -- Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? FreeBSD: Are you guys coming or what? OpenBSD: He guys you left some holes out there! pgp0.pgp Description: PGP signature
Re: ACPI problems with Compaq Evo N610c
On Mon, 1 Sep 2003, Robert [unknown-8bit] Blacquière wrote: I don't seem to have these problems. I use xbattbar without problem. Argh. How recent is your -current? I compile regularly, and I was up to date as of this afternoon. I use this acpi_dsdt code: http://www.guldan.cistron.nl/acpi_dsdt.dsl Thanks for the suggestion... I tried that one, but got the same error about not enough memory to load the override file. I attached a verbose dmesg, just in case someone wants to take a look. Doug -- This .signature sanitized for your protection ified - using default frequency Timecounter i8254 frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 1794188892 Hz CPU: Mobile Intel(R) Pentium(R) 4 - M CPU 1.80GHz (1794.19-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf27 Stepping = 7 Features=0xbfebf9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE real memory = 536674304 (511 MB) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x00503000 - 0x1f6aafff, 521830400 bytes (127400 pages) avail memory = 51598 (492 MB) bios32: Found BIOS32 Service Directory header at 0xc00fa000 bios32: Entry = 0xf (c00f) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0x3a2 pnpbios: Found PnP BIOS data at 0xc00f4330 pnpbios: Entry = f:435e Rev = 1.0 pnpbios: Event flag at f4356 pnpbios: OEM ID 4d00110e Other BIOS signatures found: null: null device, zero device random: entropy source mem: memory I/O Pentium Pro MTRR support enabled VESA: information block 56 45 53 41 00 02 00 01 00 01 01 00 00 00 22 00 00 01 ff 01 00 01 19 01 00 01 2f 01 00 01 34 01 00 01 82 01 0d 01 0e 01 0f 01 20 01 92 01 93 01 94 01 95 01 96 01 a2 01 a3 01 a4 01 a5 01 a6 01 VESA: 60 mode(s) found VESA: v2.0, 32704k memory, flags:0x1, mode table:0xc03f08e2 (122) VESA: ATI MOBILITY RADEON 7500 VESA: ATI Technologies Inc. P7 01.00 ACPI: DSDT was overridden. -0424: *** Error: UtAllocate: Could not allocate size 50204453 ACPI-0428: *** Error: Could not allocate table memory for [/* R] length 50204453 ACPI-0368: *** Error: Could not copy override ACPI table, AE_NO_MEMORY npx0: math processor on motherboard npx0: INT 16 interface acpi0: COMPAQ CPQ00B7 on motherboard pci_open(1):mode 1 addr port (0x0cf8) is 0x80010014 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=1a308086) pcibios: BIOS version 2.10 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: bus 1 dev 0 func 0 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: bus 0 dev 0 func 0 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: bus 2 dev 6 func 0 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: bus 2 dev 6 func 1 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: bus 0 dev 31 func 0 acpi0: power button is handled as a fixed feature programming model. ACPI timer looks GOOD min = 4, max = 4, width = 0 ACPI timer looks GOOD min = 4, max = 4, width = 0 ACPI timer looks GOOD min = 4, max = 4, width = 0 ACPI timer looks GOOD min = 4, max = 4, width = 0 ACPI timer looks GOOD min = 4, max = 4, width = 0 ACPI timer looks GOOD min = 4, max = 4, width = 0 ACPI timer looks GOOD min = 4, max = 4, width = 0 ACPI timer looks GOOD min = 4, max = 4, width = 0 ACPI timer looks GOOD min = 4, max = 4, width = 0 ACPI timer looks GOOD min = 4, max = 4, width = 0 Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) acpi_cpu0: CPU port 0x530-0x537 on acpi0 mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) acpi_tz0: thermal zone port 0x530-0x537 on acpi0 mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) acpi_tz1: thermal zone port 0x530-0x537 on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 initial configuration \\_SB_.C045.C0C2 irq 0: [ 5 10 11] low,level,sharable 0.31.0 \\_SB_.C045.C0C1 irq 11: [ 5 10 11] low,level,sharable 0.31.1 before setting priority for links \\_SB_.C045.C0C2: interrupts: 51011 penalty: 110 110 210 references: 1 priority: 0 before fixup boot-disabled links - \\_SB_.C045.C0C2: interrupts: 51011 penalty: 110 110 210 references: 1 priority: 143 after fixup boot-disabled links -- arbitrated
Re: ACPI problems with Compaq Evo N610c
Oeps I've put the old one up... Now ik have the new one. I don't load the VESA modules, it seems these are loaded before acpi code is replaced? Robert On Mon, Sep 01, 2003 at 01:49:42AM -0700, Doug Barton wrote: On Mon, 1 Sep 2003, Robert [unknown-8bit] Blacquire wrote: I don't seem to have these problems. I use xbattbar without problem. Argh. How recent is your -current? I compile regularly, and I was up to date as of this afternoon. I use this acpi_dsdt code: http://www.guldan.cistron.nl/acpi_dsdt.dsl Thanks for the suggestion... I tried that one, but got the same error about not enough memory to load the override file. I attached a verbose dmesg, just in case someone wants to take a look. Doug -- -- Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? FreeBSD: Are you guys coming or what? OpenBSD: He guys you left some holes out there! pgp0.pgp Description: PGP signature
Re: ACPI problems with Compaq Evo N610c
Doug Barton wrote: I use this acpi_dsdt code: http://www.guldan.cistron.nl/acpi_dsdt.dsl Thanks for the suggestion... I tried that one, but got the same error about not enough memory to load the override file. I attached a verbose dmesg, just in case someone wants to take a look. | ACPI: DSDT was overridden. | -0424: *** Error: UtAllocate: Could not allocate size 50204453 | ACPI-0428: *** Error: Could not allocate table memory for [/* | R] length 50204453 | ACPI-0368: *** Error: Could not copy override ACPI table, AE_NO_MEMORY I'm going to go out on a limb here and suggest that perhaps the problem is that the damn thing appears to be 50 Megabytes... -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI problems with Compaq Evo N610c
On Mon, 1 Sep 2003, Terry Lambert wrote: Doug Barton wrote: I use this acpi_dsdt code: http://www.guldan.cistron.nl/acpi_dsdt.dsl Thanks for the suggestion... I tried that one, but got the same error about not enough memory to load the override file. I attached a verbose dmesg, just in case someone wants to take a look. | ACPI: DSDT was overridden. | -0424: *** Error: UtAllocate: Could not allocate size 50204453 | ACPI-0428: *** Error: Could not allocate table memory for [/* | R] length 50204453 | ACPI-0368: *** Error: Could not copy override ACPI table, AE_NO_MEMORY I'm going to go out on a limb here and suggest that perhaps the problem is that the damn thing appears to be 50 Megabytes... Well, you could have verified that easily enough for yourself by downloading the file at that URL above. :) It turns out that it's only 142k, which is another reason I think that something very odd is happening. Doug -- This .signature sanitized for your protection ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ACPI problems with Compaq Evo N610c
Doug Barton wrote: On Mon, 1 Sep 2003, Terry Lambert wrote: I attached a verbose dmesg, just in case someone wants to take a look. | ACPI: DSDT was overridden. | -0424: *** Error: UtAllocate: Could not allocate size 50204453 | ACPI-0428: *** Error: Could not allocate table memory for [/* | R] length 50204453 | ACPI-0368: *** Error: Could not copy override ACPI table, AE_NO_MEMORY I'm going to go out on a limb here and suggest that perhaps the problem is that the damn thing appears to be 50 Megabytes... Well, you could have verified that easily enough for yourself by downloading the file at that URL above. :) And getting 50M, if your dmesg was right... 8-) 8-). It turns out that it's only 142k, which is another reason I think that something very odd is happening. My guesses, in order, would be (1) an unitialized variable, or (2) it loads sparsely, or (3) it has a really bogus table entry that claims it needs that much memory. It doesn't look magic enough to be a sign extension/signed-unsigned pun error. Other than starting at the code that's supposed to load the table in, and printf'ing until you find out why it's thinks 50M is a nuce number, I don't know what to tell you... -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
