On Tue, 16 Sep 2003, Damian Gerow wrote:
> Thus spake Nate Lawson ([EMAIL PROTECTED]) [16/09/03 16:24]:
> > I have no time to track this down but the output of acpidump -t may help
> > someone else who might be interested. You're looking for the pointers
> > that are stored in RSD PTR.
>
> I'm sti
Thus spake Nate Lawson ([EMAIL PROTECTED]) [16/09/03 16:24]:
> I have no time to track this down but the output of acpidump -t may help
> someone else who might be interested. You're looking for the pointers
> that are stored in RSD PTR.
I'm still on 5.1-R, and there's no '-t' flag to acpidump.
On Tue, 16 Sep 2003, Damian Gerow wrote:
> Thus spake Nate Lawson ([EMAIL PROTECTED]) [16/09/03 15:00]:
> > I'm almost certain your problem is defining MAXMEM to 512 MB. Remove that
> > from your kernel config and try again. MAXMEM causes all kinds of
> > problems. If this doesn't solve it, star
Thus spake Nate Lawson ([EMAIL PROTECTED]) [16/09/03 15:00]:
> I'm almost certain your problem is defining MAXMEM to 512 MB. Remove that
> from your kernel config and try again. MAXMEM causes all kinds of
> problems. If this doesn't solve it, start with the stock GENERIC and add
> back in your c
> (To recap: I'm having ACPI problems on a DFI CD70-SC, with both 5.1-R and
> 5-CURRENT. Booting GENERIC doesn't show any problems, however, so there's
> a good chance it's a misconfiguration issue.)
>
> Thus spake Damian Gerow ([EMAIL PROTECTED]) [15/09/03 17:34]:
> > It's attached. There's no A
(To recap: I'm having ACPI problems on a DFI CD70-SC, with both 5.1-R and
5-CURRENT. Booting GENERIC doesn't show any problems, however, so there's a
good chance it's a misconfiguration issue.)
Thus spake Damian Gerow ([EMAIL PROTECTED]) [15/09/03 17:34]:
> It's attached. There's no APM in there
Thus spake Nate Lawson ([EMAIL PROTECTED]) [13/09/03 14:42]:
> The post you reference shows the user with a kernel that has both APM and
> ACPI installed, apparently. This is not valid.
>
> Please report your kernel config. If GENERIC in 2003/9/6 booted fine with
> ACPI and then your rebuilt ker
The post you reference shows the user with a kernel that has both APM and
ACPI installed, apparently. This is not valid.
Please report your kernel config. If GENERIC in 2003/9/6 booted fine with
ACPI and then your rebuilt kernel from 2003/9/7 fails, it is almost
certainly the devices you include
On Tue, 9 Sep 2003, Dag-Erling [iso-8859-1] Smørgrav wrote:
> Nate Lawson <[EMAIL PROTECTED]> writes:
> > Please report the dmesg from boot -v as that should help figure out why
> > pci_cfgregopen() fails.
>
> Full log attached, both with and without ACPI.
Perhaps someone who knows our PCI code be
Nate Lawson <[EMAIL PROTECTED]> writes:
> Please report the dmesg from boot -v as that should help figure out why
> pci_cfgregopen() fails.
Full log attached, both with and without ACPI.
> Also, I think the following should be "\_S3":
>Name (\SS3, Package (0x04)
That shouldn't have any impac
> 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:
This is the line that triggers that panic, from
/sys/dev/acpica/Osd/OsdHardware.c:
if (pci_cfgregopen() == 0)
panic("AcpiOsDerivePciId unable to initialize pci bus");
Please report the dmesg from boot -v as that should help figure out why
pci_cfgregopen() fails.
Also, I think the fol
]>
> 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
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 allo
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 verbos
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.
|
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
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_dsd
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.
>
>
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
Hi!
I applied the patch from
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=214877+0+archive/2003/freebsd-current/20030615.freebsd-current
and the AE_BAD_PARAEMTER error disappers.
Hendrik
--
Hendrik Scholz - <[EMAIL PROTECTED]> - http://raisdorf.net/
Forcast for tonight: Dark.
___
Hi,
I'm seeing similiar things on my setup - both the ACPI Global Lock
messages and the wi0 issues. In fact, the wi driver seems to be
incredibly unstable - Every half hour or so I need to remove and
re-insert the card to regain network connectivity (and ofcourse killall
dhclient ; ifconfig wi0 ..
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks!
I have it working nicely now - without any problems.
I decompiled, fixed and compiled... problem sorted :)
On Wednesday 18 June 2003 8:58 am, Sid Carter wrote:
> On Tue, Jun 17, 2003 at 04:21:41PM +0100, Antony T Curtis wrote:
> > On a Comp
On Tue, Jun 17, 2003 at 04:21:41PM +0100, Antony T Curtis wrote:
>
> On a Compaq Armada V300 notebook, if I load the acpi module, boot fails after
> the kernel prints about half a dozen "acpi_bus_number: can't get _ADR", fails
> to detect any of the hardware and panics because of failure to moun
- Original Message -
From: "Kevin Oberman" <[EMAIL PROTECTED]>
To: "Matthew Emmerton" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, June 04, 2003 10:21 AM
Subject: Re: ACPI problems with HEAD and IBM ThinkPad T23
> > From: &qu
On Wed, Jun 04, 2003 at 10:45:21AM -0400, Matthew Emmerton wrote:
> >
> > This is The Way Things Work. Logial device attachments are no longer
> > compiled into the kernel in 5.x by default (see the entry in GENERIC
> > about this), so you need to define those attachments in the device.hints
> > f
> Matthew Emmerton wrote:
> > I cvsup'd from 5.0-R to HEAD and enabled ACPI to see if anything had
changed
> > in the past 6 months.
> > Indeed, things have, and a few workarounds I had implemented before were
no
> > longer needed.
> >
> > However, I still got a host of errors from ACPI upon boot,
Matthew Emmerton wrote:
I cvsup'd from 5.0-R to HEAD and enabled ACPI to see if anything had changed
in the past 6 months.
Indeed, things have, and a few workarounds I had implemented before were no
longer needed.
However, I still got a host of errors from ACPI upon boot, and some hacks to
device.h
> From: "Matthew Emmerton" <[EMAIL PROTECTED]>
> Date: Wed, 4 Jun 2003 10:00:53 -0400
> Sender: [EMAIL PROTECTED]
>
> This is a multi-part message in MIME format.
>
> --=_NextPart_000_0069_01C32A80.2F346810
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding:
Martin Blapp wrote:
This IBM X-Series 305 show these ACPI problems. And rebooting the box with
ACPI enabled hangs it (deadlock).
Feb 13 17:41:05 ibm-01 kernel: acpi0: on motherboard
Feb 13 17:41:05 ibm-01 kernel: ACPI-0625: *** Info: GPE Block0 defined
as GPE0
to GPE31
Feb 13 17:41:05 ibm-01 k
I placed the verbose boot dmesg's at
www.chemikals.org/acpi
and
www.chemikals.org/no-acpi
Thanks in advance for any help rendered!
On Tue, 20 Nov 2001, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Wesley Morgan writes:
> : Anyone have any ideas what the problem may be? The error mess
In message <[EMAIL PROTECTED]> Wesley Morgan writes:
: Anyone have any ideas what the problem may be? The error messages I see
: from the wavelan card seem to indicate an interrupt problem, but it gets
: the same irq w/o the module and works fine.
With all due respect, this report is too vague to
Mike Smith wrote:
> This is the general form of a different problem. The hints
> DO NOT supply PNP identifiers. Got it yet?
You are adding nothing useful in terms of forward progress
on solving his problem by commenting on my postings instead
of addressing his issues, which I have at least
> Since you posted this message to -current, I just assumed you
> had upgraded to the latest code, and thus were using ACPI (this
> is the same thing that ended up confusing Mike Smith, who also
> made the mistake in correcting me to say that ACPI was being
> loaded twice on your system).
Actuall
Pete Carah wrote:
> > Known problem... see the -current archives.
It *is* a known problem.
> > You are attaching twice: once because of ACPI, and again
> > because of the "hints". You need to comment the entries
> > out of your hints file to make them not get attached twice.
It's just not thi
Terry Lambert wrote:
>
> > unknown: can't assign resources
> > unknown: at port 0x378-0x37f on isa0
> > unknown: can't assign resources
> > unknown: at port 0x3f8-0x3ff on isa0
> > unknown: can't assign resources
> > unknown: at port 0x2f8-0x2ff on isa0
> > unknown: can't assign resourc
Mike Smith wrote:
> > > unknown: can't assign resources
> > > unknown: at port 0x3f8-0x3ff on isa0
> > > unknown: can't assign resources
> > > unknown: at port 0x2f8-0x2ff on isa0
Serial ports...
[ ... ]
> You're smoking crack, again. Hints don't supply PnP IDs.
Still a known problem...
> > unknown: can't assign resources
> > unknown: at port 0x378-0x37f on isa0
> > unknown: can't assign resources
> > unknown: at port 0x3f8-0x3ff on isa0
> > unknown: can't assign resources
> > unknown: at port 0x2f8-0x2ff on isa0
> > unknown: can't assign resources
> > unknown: at irq 12
Pete Carah wrote:
>
> I have a panic that I haven't seen in the notes so far; if I allow load
> of the acpi module, it gets a "can't allocate memory" very early in the
> boot process.
>
> Hopefully the following is complete - KDE2 cut-and-paste didn't work
> as I expected for a big region.
[ ..
I have a panic that I haven't seen in the notes so far; if I allow load
of the acpi module, it gets a "can't allocate memory" very early in the
boot process.
Hopefully the following is complete - KDE2 cut-and-paste didn't work
as I expected for a big region.
Motherboard is ASUS A7V with 1.2G pr
40 matches
Mail list logo
