Re: [ACPI-sppt] ACPI not writing to /proc/acpi/event

dsdt instructions can be found here

http://www.cpqlinux.com/acpi-howto.html

simpler instructions here

http://acpi.sourceforge.net/wiki/index.php/HowToOverrideTable

I actually used both sets of instructions to comprehend the process. 
its not too tought.

the dsdt patch is what tells the kernel to use the custom dsdt I
believe.  I had 3-4 errors in my dsdt.  The point of the dsdt process is
because there tend to be errors in the dsdt and if you can fix them, it
can fix your computer.  I don't know why it works on windows...

CL

On Wed, 2003-09-24 at 14:13, Brett Blackham wrote:
> I haven't found much about applying a dsdt patch.  From what little I've been 
> able to find it sounds like the kernel uses the system dsdt unless you tell 
> it to use a custom one.  In any case I am still very unclear about the whole 
> dsdt patch processes.  
> 
> I have tried to disassemble and rebuild my current dsdt.  I'm already off to a 
> bad start.  I get a "parse error, unexpected PARSEOP_IF" in a If statement.  
> Sad part is that syntax is char for char the same as a block of code a few 
> hundred lines above it.  Also note that I haven't change a single line of 
> code.  I even tried iasl -dc dsdt and got the same error.  When I just cut 
> that block of code out it finished compiling without any errors.  Now I have 
> a DSDT.aml file.  How do I get the kernel to use that.  (even though I 
> haven't change anything except remove that If statement so I could get a 
> clean build)  And assuming I find out how to tell the kernel to use the new 
> table where do I go to learn about ACPI-assembly so I can finally fix the 
> problem?
> 
> On Tuesday 23 September 2003 7:00 pm, Carl L. Gilbert wrote:
> > Your next step is to apply the dsdt patch.  I think it will use your
> > built in dsdt by default!?  (could someone answer that one for me?)
> >
> > Then if that does not work, time to decompile and fix your dsdt.
> >
> > Thats what I have done.  Seems like that is what you need.  Especially
> > since yours is so drastically broken it seems.
> >
> > CL
> >
> > On Tue, 2003-09-23 at 16:31, Brett Blackham wrote:
> > > No I havn't done anything with DSDT patch.  I read a little bit about it.
> > >  I stoped reading after step 3 of:
> > > http://acpi.sourceforge.net/wiki/index.php/HowToOverrideTable
> > >
> > > I could only find one dsdt table in the acpi.sf.net database and it was
> > > for a different board.
> > >
> > > On Tuesday 23 September 2003 1:19 pm, Carl L. Gilbert wrote:
> > > > I would then suggest you build the kernel with debug on.  If that does
> > > > not work, as you have suggested, then you probably need to fix your
> > > > DSDT.  Are you using a DSDT/applied the DSDT patch??
> > > >
> > > >
> > > >
> > > > CL
> > > >
> > > > On Tue, 2003-09-23 at 13:37, Brett Blackham wrote:
> > > > > Okay, I havn't been 100% open with you.  I do have acpid 1.0.2
> > > > > installed. I have it start up in the rc3.d.  I would first tail -f
> > > > > /var/log/acpid and /var/log/messages then press the power button. 
> > > > > Then I would shutdown acpid and then cat /proc/acpi/events.  (I
> > > > > couldn't cat it when acpid was running). I also had acpid configured
> > > > > with the event/default calling a sciprt that would just log what it
> > > > > recived like so: $1 >> /tmp/1.log and $2 >> /2.log. Thus I feel its
> > > > > safe to say ACPI is not sending any messages.
> > > > >
> > > > > In my many kernel builds I did some with debug and some without. 
> > > > > Result was the same.  I wouldn't recive any /var/log/messages or
> > > > > /var/log/acpid events and my /tmp/2.log and 1.log files would be
> > > > > empty.
> > > > >
> > > > > On Tuesday 23 September 2003 10:29 am, Carl L. Gilbert wrote:
> > > > > > you are not running acpid are you? if not try installing that and
> > > > > > seeing what it says.
> > > > > >
> > > > > > Didi you build your kernel with ACPI debugging enabled?  If not,
> > > > > > rebuild with ACPI enabled so you can see the events in the log.
> > > > > >
> > > > > >
> > > > > > CL
> > > > > >
> > > > > > On Tue, 2003-09-23 at 12:18, Brett Blackham wrote:
> > > > > > > I've never cared much more modules so I've been building it all
> > > > > > > into the kernel.  As for the monitoring I was just doing a 'cat
> > > > > > > /proc/acpi/events'. Thanks for the feedback can you think of
> > > > > > > anything else I might try.
> > > > > > >
> > > > > > > On Monday 22 September 2003 10:20 pm, Carl L. Gilbert wrote:
> > > > > > > > make sure you build the stuff into the kernel.  if you make the
> > > > > > > > stuff modules, make sure you load the modules before you try to
> > > > > > > > use ACPI stuff.
> > > > > > > >
> > > > > > > > as for the one time events, make sure you are monitoring it
> > > > > > > > correctly. I had that problem but it was because of my
> > > > > > > > monitoring script I created.
> > > > > > > >
> > > > > > > > CL
> > > > > > > >
> > > > > > > > On Mon, 2003-09-22 at 19:52, Brett Blackham wrote:
> > > > > > > > > I have ACPI built into the kernel but I can't see any
> > > > > > > > > messages in event when I cat it.  I played around with a
> > > > > > > > > couple of different kernels and got it to work for a little
> > > > > > > > > bit.  When it was working I could only press the power button
> > > > > > > > > once and it would receive that one event.  When I pressed it
> > > > > > > > > again nothing was sent.  It would not receive an event until
> > > > > > > > > I powered down and back up.  In my attempt to get it working
> > > > > > > > > 100% of the time I seemed to have broken it further. I can't
> > > > > > > > > even get it to receive the first message now.  I tried nearly
> > > > > > > > > every combo of kernel .config but can't get it back the way
> > > > > > > > > it once was.   I didn't save the .config file of the almost
> > > > > > > > > working kernel but I'm sure in my nearly 30 different kernel
> > > > > > > > > builds and BIOS configs I've came across the same kernel
> > > > > > > > > config which leads me to believe its buggy.  (Guess thats why
> > > > > > > > > I had to select allow experamental code to get the ACPI
> > > > > > > > > section)
> > > > > > > > >
> > > > > > > > > Does anyone have any suggestions on how I might get this
> > > > > > > > > working?
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > System:  Redhat 8.0 base w/ Gentoo hardened 2.4.21 kernel.
> > > > > > > > > Motherboard: Tyan S2721-533 V1.01
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > -------------------------------------------------------
> > > > > > > > > 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
> > > > > _______________________________________________
> > > > > 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
> > > _______________________________________________
> > > ACPI-support mailing list
> > > [email protected]
> > > https://lists.sourceforge.net/lists/listinfo/acpi-support
-- 
Thank you,


CL Gilbert
"Then said I, Wisdom [is] better than strength: nevertheless the poor
man's wisdom [is] despised, and his words are not heard." Ecclesiastes
9:16

GnuPG Key Fingerprint:
82A6 8893 C2A1 F64E A9AD  19AE 55B2 4CD7 80D2 0A2D
GNU Privacy Guard http://www.gnupg.org (Encryption and Digital
Signatures)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQA/cgbuVbJM14DSCi0RAjeZAJ9T5B1epV9+s/wfQkiqDvb+oHSWXgCgkYYN
fkpoXZZIXuPLt2KXw0xNyJQ=
=+maT
-----END PGP SIGNATURE-----