Ok, set it as invalid.
Thanks.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
acpi=force required for Acer Aspire 1315
https://bugs.launchpad.net/bugs/83111
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
Hmm, I see that I didn't update in a while. In the meantime I did
upgrade my BIOS, which (of course) fixed the problem because the BIOS
age was now new enough. This also means that I cannot test anymore. I
suggest closing this bug - the laptop age reaches end-of-life for most
users, it's now not po
The 18 month support period for Edgy Eft 6.10 has reached it's end of
life. As a result, we are closing the linux-source-2.6.17 Edgy Eft
kernel task.
** Changed in: linux-source-2.6.17 (Ubuntu)
Status: Confirmed => Invalid
** Tags added: edgy-close
** Also affects: linux (Ubuntu)
Impo
Hardy Heron 8.04 was recently released. It would be helpful if you
could test the new release and verify if this is still an issue -
http://www.ubuntu.com/getubuntu/download . You should be able to test
your bug using the LiveCD. Please let us know your results. Thanks.
** Changed in: linux (U
It boots fine again with kernel 2.6.20-16 (latest Feisty) without the
acpi=force option. ACPI doesn't work then, however, but it doesn't hard-crash
anymore on startup :-)
Still didn't do a BIOS-update btw... (need to find a floppy, some dos image,
put it on, etc...)
--
acpi=force required for
** Changed in: linux-source-2.6.17 (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Ubuntu Kernel Team
Status: Needs Info => Confirmed
--
acpi=force required for Acer Aspire 1315
https://bugs.launchpad.net/bugs/83111
You received this bug notification because you
** Attachment added: "lspci-vvnn.log"
http://librarian.launchpad.net/7223182/lspci-vvnn.log
--
acpi=force required for Acer Aspire 1315
https://bugs.launchpad.net/bugs/83111
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
u
** Attachment added: "dmesg.log"
http://librarian.launchpad.net/7223180/dmesg.log
--
acpi=force required for Acer Aspire 1315
https://bugs.launchpad.net/bugs/83111
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Thanks for the reply. I did not yet update my bios, didn't yet find the
time (and a floppy well enough) to do it. It remains on my todo list,
but yesterday I thought that if Ubuntu is designed to run out-of-the-box
it shouldn't crash on a kernel dump anyways, so I did steps 1-4 today. I
will update
I can confirm the same symptoms as the original post, but on a desktop
machine with the VIA KT400/KT600 chipset.
2.6.15 (Edgy) worked fine.
2.6.17 (Edgy) required the acpi=force option.
--
acpi=force required for Acer Aspire 1315
https://launchpad.net/bugs/83111
--
ubuntu-bugs mailing list
ubu
Change Status of Unconfirmed to Needs Info.
** Changed in: linux-source-2.6.17 (Ubuntu)
Status: Unconfirmed => Needs Info
--
acpi=force required for Acer Aspire 1315
https://launchpad.net/bugs/83111
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailma
Thanks for taking the time to report this bug. Unfortunately we can't
fix it, because your description didn't include enough information.
Please include the following additional information, if you have not already
done so (please pay attention to lspci's additional options), as required by
the
Today I accidentally booted 2.6.15-25, since it was still my default. It
hung somewhere after the fsck (can't see where exactly, since on-screen
logging verbosity has decreased a lot). Booting into 2.6.17 did also
show the fsck screen for a short time, then going to X. So: acpi=force
makes 2.6.15-2
** Changed in: Ubuntu
Sourcepackagename: None => linux-source-2.6.17
--
acpi=force required for Acer Aspire 1315
https://launchpad.net/bugs/83111
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
14 matches
Mail list logo
