** Changed in: fwts (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/897298
Title:
fwts should test chassis type
To manage notifications about
** Changed in: fwts (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/897298
Title:
fwts should test chassis type
To manage notifications about this
I create deb packages with changes in comment#8.
The debs can be downloaded from
http://zinc.canonical.com/~alexhung/lp-897298/
It will be executed by sudo fwts dmi_decode and save the errors, if
any, to results.log.
--
You received this bug notification because you are a member of Ubuntu
SMBIOS and ACPI specifications has some similar definitions for chassis
type and battery
SMBIOS Type 3 (Chassis Type) -- ACPI FADT-Preferred_PM_Profile
SMBIOS Type 22 (Portable Battery) --- ACPI Battery device
The other way to solve the this problem is the compare SMBIOS and ACPI
by the above;
** Changed in: fwts (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/897298
Title:
fwts should test chassis type
To manage notifications about this bug go
@Colin,
I agree with your 1 + 2. Nothing stops engineers designing a small
battery to avoid sudden power loss. I guess some industrial PC may see
the need to install a battery.
Some ideas:
1. It would be a good idea to compare FADT and DMI. The challenge would
be how to match DMI's definition
Well, there are some different ways of approaching this. Either we
physically state the machine is meant to be a specific machine type
using a command line option or we try to infer it (e.g. has it got a
battery, then 'probably' it's a mobile platform of some sort).
Perhaps we should have a
Here's some survey data of a sample of systems, we did this to check
how reliable the DMI type information is.
First we tested on 77 portable systems, laptops and netbooks. Here's a
breakdown:
1 Desktop
3 Other
5 Laptop
30 Notebook
38 Portable
Next, a test on 40
Instead of checking for /proc/acpi/battery, this is what we actually
tried: sudo find /sys -name 'type' -exec grep --color=never -H 'Battery'
{} \;
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/897298
We should also check against the ACPI FADT table that contains the model
type (e.g. mobile, desktop etc) and correlate this with the DMI data.
Section 5.2.9 of the ACPI spec, Preferred_PM_Profile may help us infer that the
system should have a battery or not.
Section 7.4.1 of the SMBIOS spec
@Daniel, I'd be interested to see how it breaks down for laptops and
netbooks too.
** Changed in: fwts (Ubuntu)
Assignee: (unassigned) = Alex Hung (alexhung)
** Changed in: fwts (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of
@Colin, this bug was mostly intended to share our experience with a
particular weakness in DMI data which sometimes reports invalid chassis
information. It seemed relevant to add this test to fwts since it
already tests for invalid or incomplete DMI data, like the system vendor
set to To Be Set By
12 matches
Mail list logo
