N340S8 laptop needs to have ACPI enabled

Tomasz, after booting with acpi=force, please update the report with the output of "uname -a", and please attach the output of the following commands:

sudo lspci -vv

sudo lspci -vvn

sudo dmidecode

Please be sure to use sudo, root privileges are required to obtain the necessary information. Please attach one file per command, please do not compress the output, please do not add the output in-line, and please do not attempt to email in the attachments - they have to be added to the report within Launchpad.

It would also be useful if you could create a wiki page for your laptop; please refer to [1].

Thanks!

[1] https://wiki.ubuntu.com/LaptopTesting

tom@srebrny:~$ uname -a
Linux srebrny 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux

Marking this whitelist request as confirmed, based on having sufficient information about the machine. Leaving at acpi-support since I don't know where else to put it! White-listing this machine will probably be a job for Gibbon, yes?

Unassigning as I am no longer able to triage/monitor.

So what am I supposed to do now?

On 6/6/07, Peter Whittaker <email address hidden> wrote:
> Unassigning as I am no longer able to triage/monitor.
>
> ** Changed in: acpi-support (Ubuntu)
> Assignee: Peter Whittaker => (unassigned)
>
> --
> N340S8 laptop needs to have ACPI enabled
> https://bugs.launchpad.net/bugs/92806
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Tomasz Dominikowski
http://www.skyos.org | http://wiki.ubuntu.com/TomaszDominikowski
"Brian, let us pray. Dear Lord... stay out of our way!"

This bug also exists in Gutsy (uptodate as of 19th September).

I don't think this is an acpi-support bug; acpi-support doesn't have any kind of cut-off age. I think it's just that the kernel got stricter and needs to have a quirk added for this hardware. Kernel team?

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

Is it also their policy to ignore a bug for 18 months? This obviously affects both 2.6.24 and 2.6.27. :(

Hrm, it's likely this issue has been overlooked because it wasn't assigned to the correct kernel package. Beginning with the Hardy development cycle kernel bugs should be reported against the 'linux' kernel package rather than linux-source-2.6.xx. I have added the 'linux' task. However, note that the kernel is now frozen for Intrepid so it's likely this will need to be addressed in Jaunty. Additionally, the 18 month support period for Feisty Fawn 7.04 has reached it's end of life - http://www.ubuntu.com/news/ubuntu-7.04-end-of-life so the linux-source-2.6.20 kernel task will be closed. Thanks.

@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.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on the current status, under the Status column, and change
the Status back to "New". Thanks again!

The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
linux-source-2.6.22 kernel task. It would be helpful if you could test the
new Jaunty Jackalope 9.04 release and confirm if this issue remains -
http://www.ubuntu.com/getubuntu/releasenotes/904overview. If the issue still exists with the Jaunty
release, please update this report by changing the Status of the "linux (Ubuntu)"
task from "Incomplete" to "New". Also please be sure to run the command below
which will automatically gather and attach updated debug information to this
report. Thanks in advance.

apport-collect -p linux-image-2.6.28-11-generic 92806

The linux task was already closed by the kernel team due to lack of information. Closing again; it can be reopened if someone provides the requested information.