Re: ACPI problems with this morning's -CURRENT [SOLVED]

2003-09-16 Thread Nate Lawson
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

Re: ACPI problems with this morning's -CURRENT [SOLVED]

2003-09-16 Thread Damian Gerow
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.

Re: ACPI problems with this morning's -CURRENT [SOLVED]

2003-09-16 Thread Nate Lawson
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

Re: ACPI problems with this morning's -CURRENT

2003-09-16 Thread Damian Gerow
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

Re: ACPI problems with this morning's -CURRENT

2003-09-16 Thread Nate Lawson
> (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

Re: ACPI problems with this morning's -CURRENT

2003-09-15 Thread Damian Gerow
(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

Re: ACPI problems with this morning's -CURRENT

2003-09-15 Thread Damian Gerow
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

Re: ACPI problems with this morning's -CURRENT

2003-09-13 Thread Nate Lawson
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

ACPI problems with this morning's -CURRENT

2003-09-07 Thread Damian Gerow
I set up a box yesterday to play with -CURRENT on. I used the 2003-09-06 snapshot code from ftp://current.freebsd.org/. Initial setup and boot worked just fine, but when I did a rebuild/reboot last night, this is what I saw: pmap_mapdev: Couldn't alloc kernel virtual memory So thinking I mi