All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dimitri Van Landuyt <dimitri.vanlanduyt@gmail.com>
To: linux-acpi@vger.kernel.org
Subject: MSI S420 (based on MS-141214 barebone)
Date: Fri, 06 Oct 2006 13:24:36 +0200	[thread overview]
Message-ID: <eg5edj$m49$1@sea.gmane.org> (raw)

Dear acpi list,

I bought me a brand new laptop, MSI S420 based on the MS-141214 
barebone): http://www.msicomputer.com/NB/product_spec.asp?model=MS-141214.

Of course, and too bad, not everything is supported in terms of acpi and 
  I am eager to look into this problem. I will enumerate on my issues 
and  observations here, hoping some willing ear would lend a helping hand.

I am running ubuntu edgy beta now which runs the 2.6.17-10 kernel and I 
have seen the same issues in ubuntu dapper which has a 2.6.15 kernel.

1. When booting the machine in a default configuration, it hangs (kernel 
does not respond to any sysrq key combinations) after the following lines:

using HPET for base-timer
using HPET for gettimeofday
Detected 2000.186 MHz processor
Using hpet for high-res timesource.

Playing with some kernel parameters, I notice the following behaviour: 
no effects with pci=noacpi, acpi=force,noapic, nohpet, ...
What does work is: acpi=off but then I have no acpi at all, another 
option I discovered is hpet=disable, which enables some of the acpi 
functionalities.

2. with the hpet=disable parameter, I can see battery state, but 
remainng time is calculated incorrectly (always giving the same amount 
of minutes), plugging in and out the adapter is recognized however. 
Reading temperature does not work as he always gives the constant heat 
of 75 degrees. Cpu frequency scaling does not work.

3. output of dmesg | grep ACPI and dmesg are in attachment.

4. While booting the kernel, but apparently before putting things in the 
kernel log, some messages appear (three), among which something about a 
BIOS bug. They flash away too fast for me to write them down, so a way 
of capturing these is appreciated.

5. Would fixing the DSDT (of which I read some stuff here and there) be 
helpful in my case? Is it dangerous? Is there someone to walk me through it?

6. My BIOS is v1.01 and is definitely the current version as it is a 
very new laptop in general.

Any help is greatly appreciated!

Dimitri Van Landuyt



             reply	other threads:[~2006-10-06 11:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-06 11:24 Dimitri Van Landuyt [this message]
2006-10-20 14:19 ` MSI S420 (based on MS-141214 barebone) Dimitri Van Landuyt
2006-10-20 15:10   ` Alexey Starikovskiy
2006-10-21  0:01     ` Dimitri Van Landuyt

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='eg5edj$m49$1@sea.gmane.org' \
    --to=dimitri.vanlanduyt@gmail.com \
    --cc=linux-acpi@vger.kernel.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.