Re: [ACPI-sppt] RAMB values

Hi,

Does this mean, that if you hardcode the RAMB into the dsdt, it is no
longer necessary to hardcode other values such as the trip point and fan
rpm's ??

I didn't get the last part of the message. If you hardcode the RAMB into
the dsdt, you are only able to boot without the display on, and hence can
only do a remote login. Correct ??

Mads

On Mon, 22 Sep 2003, Robert Vollmert wrote:

> > > As an immediate consequence, you can avoid the hang-on-reboot by
> > > hardcoding RAMB to 0x64646464 in the DSDT (haven't tested this).
> > >
> >
> > Another possibility is that acpi is buggy, and do not handle correctly
> > a read of a dword from an indexed field.
>
> Yes, that appears to be the case. I reported the bug on -devel. By
> hardcoding RAMB to 0x0F75064, the thermal zone and fan control work
> fine without other modifications.
>
> The only problem left is that the computer hangs during ACPI
> initialization, when executing \_SB.PCI0.VGA._INI. A temporary
> work-around is to comment out the body of that method.
>
> The cause for this appears to be some kind of conflict with other
> parts of the kernel accessing the graphics card -- if I disable the
> vga console, the kernel boots fine, though I can currently only log in
> via the network. I haven't succeeded in starting X yet, and am
> currently experimenting with the framebuffer console.
>
> Cheers
> Robert
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> ACPI-support mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/acpi-support
>


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf