From: Gabe Sibley <gsibley-DG7SOAwx7rg@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: S3 on a Compaq Evo N610c
Date: Mon, 02 Feb 2004 01:59:14 -0800 [thread overview]
Message-ID: <401E1F72.3080300@usc.edu> (raw)
Hi all,
I've got a scary storie to tell. The other day I was checking out the
acpi support on my Compaq Evo n610c. I have the latest bios from
compaq, and I was trying out the 2.6.1 stock kernel. I build the acpi
modules into the kernel. When I pipe a "3" to /proc/acpi/sleep the
system seems to go down just fine. But when I try to power up, she just
lets out a continuous beep. I had to take the battery out to reset it.
Then at as I'm booting, grub freaks out. Somehow, grub.conf was
gone... wtf? grub.conf lives on /hda2, which was never mounted. I
re-wrote grub.conf, but don't really know what happened... where did it
go? why? THe next boot cycle, /hda5 (home) complains, so I fsck it,
and find a few inode problems that I just let fsck fix. Next boot, grub
is completely gone from the boot sector, and the machine boots straight
to Windows! At this point I'm worried big time. I have run all the
compaq diagnostics to see if the disk is messedup - it's not. I
re-installed grub, and I've gone back to 2.6.0. I have not tried echo 3
again. So I have no idea what happened. Seems the laptop freaked out.
anyone else see anything like this before?
On another note, has anywone gotten acpi to *really* work on the n610c???
cheers, Gabe
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next reply other threads:[~2004-02-02 9:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 9:59 Gabe Sibley [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-03 7:44 S3 on a Compaq Evo N610c Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401CBB66E-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-02-03 9:09 ` Thorsten Zachmann
2004-02-03 9:36 ` Thorsten Zachmann
2004-02-03 9:14 Yu, Luming
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=401E1F72.3080300@usc.edu \
--to=gsibley-dg7soawx7rg@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox