Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
HP 900 Omnibook Laptop, PII and PIII (mine and my son's)
SuSE 8.1
APM or ACPI (didn't catch which) worked fine right after the installation and
indicated whether the system was on battery or power but then stopped working
as soon as the system was rebooted after that.
That is, do the install, let it finish, login as yourself into KDE and see that it
works. Reboot and it's all dead.
I have tried turning off ACPI but then the kernel panics at the point where APM
is being enabled.
I have made no changes to the system or kernel since the installation, so it's not
something I introduced.
Hello,
Yor bios probably doesn't work to well with acpi, probably best to disable acpi with kernel-parameter acpi=off at boot. This should allow apm to load instead and things might work again after that.
As to "acpi=off", the last time I tried that (I can do it
again) it panicked the kernel on boot and would not net
me get past until I either turned both apm AND acpi off,
or turned acpi back on. (Safe mode works and turns them
both off.)
I'll try again later when I get a chance.
On my son's system, it all worked fine after the install
until his next reboot. It stopped then and hasn't worked
since. That matches my experience; it works fine once
and then goes away on the next reboot.
Very frustrating. Also, I can't get the kernel to build right
now due to errors. I'm going to have to find out why it
won't rebuild right out of the box. (No changes made at
all since installation.) In one case it was due to a kdb
call (that certainly looked legal in traps.c when I looked at
it) and the latest one was in a new place.
Hello,
I use SuSE8.1 as well, and had similar problems to what you discribe with my Acer laptop. I first thought that it was due to acpi not being anabled in the kernel properly. So I reconfigured and then complied a new kernel. (I turned KDB off becuase the kernel wouldn't complie with it on.)
This didn't help so I switched off acpi at boot, to allow apm to load instead. I think which ever is loaded first is used. I guess I was lucky. I also need the kernel-parameter apm=acertm5 for my laptop. Is there a similar command for your laptop?
have you tried (might do something interesting:-):
pci=acpi
My first compile problem was also the KDB error. I think
I explicitly turned it on to try to resolve the error; maybe
I'll try turning it off and rebuilding. (Where did you turn it
on or off? I tried doing it as an option to make...)
I haven't tried anything like the pci command, just acpi=off
which gets me a kernel panic. I'm not sure where I can
get any parameters to apm; I'm on an HP900B. I may
try yours just for the heck of it.
I did try the various options and they all ended up in a
kernel panic again... :-(
I also checked out the same SuSE 8.1 release on my Dell
and it is using APM and it works great! So whatever it is
must somehow be specific to the HP Omnibook 900.
I have another lead or two to follow (check to see that the
BIOS message reports that APM is 1.2...). I don't hold a
lot of hope for this without somehow getting into all of the
code and looking at it... Yuck...
I rebuilt my kernel (and may have made some errors in overlaying my newly
built kernel over the lib/modules used by the previous one, etc... ) and rebooted
using it and found that APM worked great! Wow, nice... BUT...
I rebooted for some reason (probably a hung system again) and found that I'm
back to square one. It no longer works, panics the kernel when trying to start
PCMCIA, and is generally dead. If I put APM and ACPI back on (ACPI will then
disable APM) then I can get past the kernel panic, BUT ACPI doesn't work for
me either. (I can't find anything that tells me how to set up events, deal with
the messages from KDE, etc... I guess everyone just forgot that some of us
didn't actually write all of the code. I get references to old documents, and
circular references to out of date stuff that doesn't help at all. If you know of
anything that tells me how to enable ACPI and get it to work, I can use that
as well.)
So, I'm back to square one now. I have since cleaned up my kernel build to
ensure that everything is clean, rebuilt and consistent. I can still boot nicely in
safe mode as well, though APM and ACPI are both disabled.
My sequence has been:
make xconfig
make clean
make bzImage
make modules
su
make modules_install
cp kernel and system.map into /boot, etc.
reboot...
Do you know if there is anything that APM writes into a file someplace
that I can clear and start over? I haven't found any such files so far that
would explain why it only ever works once. (Haven't checked my home
directory yet though...)
I found that there was a message that I didn't ever understand
until... I updated to the 2.4.20 kernel. The message indicated that
my power management configuration was "incomplete" and that I
should enable "Control Method Battery" and rebuild my kernel. That
method is NOT in 2.4.19 but is in 2.4.20.
I now have a 2.4.20 kernel which does APM correctly. That's the
good news. The bad news is that my sound (Maestro 2E) has now
stopped working (the kernel complains about not finding the
file/module) and when I try to run "mkinitrd" I get a "failed mount"
error. Apparently there's something funky about my file system
support in the kernel.
With 2.4.20 I can boot with "acpi=off" without getting a kernel
panic at the PCMCIA startup. (That's where the other problem was;
it was trying to start my ethernet card and I'm assuming dying in
the network/cardbus/dhcp initialization.)
I have built a 2.4.20 kernel, have it running right now as I type this, and APM is
working fine. (There was a note in 2.4.20 that APM had been reworked/fixed.)
I now have everything working and I can see my power status on the lower bar in
KDE.
Wow... that's great! I shall try that over the weekend. Wish me luck!
Quote:
Originally posted by larryl719 I think this is closed now for me. Yea!!
I have built a 2.4.20 kernel, have it running right now as I type this, and APM is
working fine. (There was a note in 2.4.20 that APM had been reworked/fixed.)
I now have everything working and I can see my power status on the lower bar in
KDE.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.