@Tomasz -- sorry this has taken so long to get to, as Leann indicates
its been hanging about in limbo on the wrong component and all our work
is component oriented. Sorry about that.
I note from your description that you suggest that there was a patch for
this system in the dapper/edgy timeframe that went away in feisty? I
actually cannot find any specific exclusions for this system. There is
however some changes around the feisty transition to the routines which
calculate the date of the bios, so it is possible that yours was
categorised differently either side of that change.
I assume that you are seeing this message here when you boot:
if (year < CONFIG_ACPI_BLACKLIST_YEAR) {
printk(KERN_ERR PREFIX "BIOS age (%d) fails cutoff (%d), "
"acpi=force is required to enable ACPI\n",
year, CONFIG_ACPI_BLACKLIST_YEAR);
return 1;
}
somewhere in your dmesg output. It would be handy to have that from a
recent boot attached to this bug. The actual 'calculated' date reported
there may shed some light.
So please could you attach the output of the 'dmesg' command from a
recent boot.
** Changed in: linux (Ubuntu)
Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) => Andy Whitcroft (apw)
Status: Triaged => In Progress
--
N340S8 laptop needs to have ACPI enabled
https://bugs.launchpad.net/bugs/92806
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
