From: Marius Oancea <mariuso-db4prxYhZ5Fhl2p70BpVqQ@public.gmane.org>
To: acpi <acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: ACPI 20020829 and kernel 2.4.19-4GB #1 Fri Sep 13 13:14:56 UTC 2002 i686 on Gericom Supersonic M6T
Date: Fri, 22 Nov 2002 12:22:04 -0800 [thread overview]
Message-ID: <3DDE91EC.2090207@sec.co.ro> (raw)
Hi, I have an Gericom M6T and I just installed SuSE 8.1.
If u add pci=acpi to the bootparam, acpi is working nearly acceptable :
- acpi events are not raported anymore
- when i start /stop acpid (at the time of acpi modules insertion) the
complete system crash
I tried to compile a original 2.4.19 kernel (from kernel.org) and
patch this kernel with acpi-20020918-2.4.19.diff.
After that, acpi is working very well, but ... I don't have the exotic
features of SuSE anymore (PCMCIA driver is not the last one and is not
stable enough, SuSE hardware autodetection is not working too .... ,
grub, orinocco wireless card neither).
So, hopefully somebody in this list has a patch for the SuSE 8.1
kernel. The most stable acpi for Gericom Supersonic M6T is acpi-20020918.
Should I address this question to another list ?
If yes, on wich list ?
With all my respect
Marius OANCEA
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next reply other threads:[~2002-11-22 20:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-22 20:22 Marius Oancea [this message]
[not found] ` <3DDE91EC.2090207-db4prxYhZ5Fhl2p70BpVqQ@public.gmane.org>
2002-11-22 11:33 ` ACPI 20020829 and kernel 2.4.19-4GB #1 Fri Sep 13 13:14:56 UTC 2002 i686 on Gericom Supersonic M6T Maier Gerfried
-- strict thread matches above, loose matches on Subject: below --
2002-11-22 10:49 joerg.beyer-htSm2yLGOjU
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=3DDE91EC.2090207@sec.co.ro \
--to=mariuso-db4prxyhz5fhl2p70bpvqq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=mariuso-QShcZ35DvxU@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.