linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ondrej Zary <linux@rainbow-software.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Debugging APM - cat /proc/apm produces oops
Date: Tue, 25 Jul 2006 22:11:40 +0200	[thread overview]
Message-ID: <200607252211.41038.linux@rainbow-software.org> (raw)
In-Reply-To: <1153854921.4725.22.camel@localhost>

On Tuesday 25 July 2006 21:15, Alan Cox wrote:
> On Sul, 2006-07-23 at 16:30 +0200, Ondrej Zary wrote:
> > Hello,
> > cat /proc/apm produces oops on my DTK notebook. Using "apm=broken-psr"
> > kernel parameter fixes that but I lose the battery info. I'd like to have
> > the battery info (and it works fine in Windows) so I want to debug it and
> > (hopefully) fix.
>
> If broken-psr is needed can you also send me a dmidecode and lspci -vxx
> dump so I can automate that bit.

I just found that there is another problem with this machine - DMI :)
Both kernel and dmidecode says that the DMI is not present - so one would say 
that the BIOS does not support DMI.
But wait... HWiNFO32 for DOS shows working DMI 2.0 with real data (although 
some data is from Intel Trajan reference board, apparently not changed by 
BIOS engineer...)
Examining $F000 BIOS segment revealed that the "_DMI_" signature is not 
present. But there is "_DMI20_" - and the header does not seem to match. I 
can see all the strings (like "Trajan") there...
Anyone interested in BIOS dump?

-- 
Ondrej Zary

  reply	other threads:[~2006-07-25 20:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-23 14:30 Debugging APM - cat /proc/apm produces oops Ondrej Zary
2006-07-23 14:41 ` Ondrej Zary
2006-07-23 15:06 ` Stephen Rothwell
2006-07-23 16:35   ` Ondrej Zary
2006-07-24 21:51   ` Ondrej Zary
2006-07-25 20:04   ` Ondrej Zary
2006-07-25 19:15 ` Alan Cox
2006-07-25 20:11   ` Ondrej Zary [this message]
2006-07-25  7:46 Chuck Ebbert

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=200607252211.41038.linux@rainbow-software.org \
    --to=linux@rainbow-software.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).