I had the same problem on a Toshiba Portege 3480CT, same RAM. I am
running a minimal Xubuntu.
I have noticed that:
- startup was slow too, so it is not something related to X
- processor usage was at 100% even doing nothing!!
- old feisty kernel was ok, so it was the kernel somehow
I can confi
** Tags removed: hardy-kernel-candidate
--
Xubuntu Gutsy release candidate very slow
https://bugs.launchpad.net/bugs/152477
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
Can confirm that speed issues are fixed in hardy kernel. Thanks!
--
Xubuntu Gutsy release candidate very slow
https://bugs.launchpad.net/bugs/152477
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubun
Hi Jack,
That's so good to hear the speed issue is resolved as well as
suspend/resume. If you don't mind, can you open a new bug report
against the 'linux' package for the issue you are seeing with your
Netgear card on the 2.6.24 kernel. Feel free to subscribe me to the
report as well and I'll m
Leann, the speed issues have been resolved in this kernel. Also suspend to ram
works (it didn't work in feisty or gutsy, but did in edgy.)
All in all a great result, except that my Netgear WG511 v1 (prism54) card no
longer works. The attached dmesg shows the error (at the end of the file.)
Many t
Jack, here are some quick instructions that may help. Sorry, I should
have included this in my original request.
1) edit the file /etc/apt/sources.list and add the following line:
deb http://archive.ubuntu.com/ubuntu hardy main restricted
2) sudo apt-get update
3) sudo apt-get install linux-ima
http://packages.ubuntu.com/hardy/base/linux-image-2.6.24-1-generic
--
Xubuntu Gutsy release candidate very slow
https://bugs.launchpad.net/bugs/152477
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubu
I can't find linux-image-2.6.24-1-generic in the hardy repository - it still
has 2.6.22-14. I'm looking in http://packages.ubuntu.com/hardy/base/ .
Could you give me the correct link.
Many thanks.
--
Xubuntu Gutsy release candidate very slow
https://bugs.launchpad.net/bugs/152477
You received th
Hi Jack,
The Hardy Heron 2.6.24 kernel was released recently. Can you try
installing this newer kernel (linux-image-2.6.24-1-generic) and let me
know if this issue still exists? If it still exists, can you attach the
dmesg output from this newer kernel. Thanks!
** Also affects: linux (Ubuntu)
** Changed in: linux-source-2.6.22 (Baltix)
Status: New => Invalid
--
Xubuntu Gutsy release candidate very slow
https://bugs.launchpad.net/bugs/152477
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing l
Thanks for your suggestion Leann.
Unfortunately neither "lapic" nor "acpi=off" make any difference to the speed.
I'm using the Feisty kernel like Thom.
It seems to me as though it's not using the processor properly - there is no
thrashing of the hard drive.
--
Xubuntu Gutsy release candidate ver
My workaround to this issue was simply to configure grub to boot the
feisty kernel by default, since the gutsy kernel is unusable. Hoping
this gets fixed for Hardy.
--
Xubuntu Gutsy release candidate very slow
https://bugs.launchpad.net/bugs/152477
You received this bug notification because you
Hi All,
Thank you for all of your comments and information.
Jackdaw28, I noticed in the dmesg output you've attached that the Local
APIC has been disabled by your BIOS:
Local APIC disabled by BIOS -- you can enable it with "lapic"
Care to try enabling it with the "lapic" kenel boot option and l
** Also affects: linux-source-2.6.22 (Baltix)
Importance: Undecided
Status: New
--
Xubuntu Gutsy release candidate very slow
https://bugs.launchpad.net/bugs/152477
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubunt
installed bootchart, but can't open the generated files. Attaching.
Note that I've done boots on both gutsy and feisty kernels.
On the feisty kernel right now.
** Attachment added: "bootchart.svgz"
http://launchpadlibrarian.net/10081058/bootchart.svgz
--
Xubuntu Gutsy release candidate ver
Hi guys, I was browsing the forums and I got into this thread:
http://ubuntuforums.org/showthread.php?t=579622
Could you install bootchart and see what is taking the most to load?
Maybe it's also usplash like on that thread. In any case, we'll gain
more insight.
--
Xubuntu Gutsy release candidat
Miguel, thanks for trying.
I'll be away on holiday until 25th October and so won't be able to try anything
that the kernel team suggest until then.
--
Xubuntu Gutsy release candidate very slow
https://bugs.launchpad.net/bugs/152477
You received this bug notification because you are a member of U
By the way, I don't really think the "unstable clocksource" is really
the culprit of performance issues. On the kerneltrap link, they said it
would cause a delay of about 6-10 seconds which, although long, it still
small compared to the delays you guys are commenting. And before I
forget, I'm also
OK, I'm assigning the bug to the ubuntu-kernel-team as this most
decidedly looks like a kernel issue. Furthermore, they'll be able to
provide more insightfull comments than I do.
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
--
Confirmed on a Toshiba Satellite 2250CDT. (Celeron M, 600Mhz, 192 MB
RAM)
This laptop, while not a fast laptop by any means, worked great with
Xubuntu 7.04. With the new kernel in 7.10, boot has gone from about 40
seconds to something on the order of 3 minutes. Once Gnome loads
(slowly), the who
Thanks for your suggestions.
Those options didn't work unfortunately.
I suspect that it's related to this bug: http://kerneltrap.org/node/8306
I'm not sure how to fix it with the suggestions there.
How can I assign it to the kernel team?
--
Xubuntu Gutsy release candidate very slow
https://bugs.l
The only thing I imagine is a conflict in apic or acpi or things like
those. Have you tried the "noapic" and "nolapic" boot options? And
"noacpi"? I know it's vague, but I'm at a loss. The only other thing I
can think of doing is assigning the bug to the ubuntu kernel team, so
that it gets looked b
I've done a clean install from the alternate installer for the release
candidate but it's just as bad.
The install itself took about 12 hours as opposed to 45 minutes for Feisty.
I've attached dmesg for the clean install.
Please advise me upon what should I check next.
** Attachment added: "dmesg
I was actually referring to the I/O issue. I know that trackerd is not
the only culprit, because, personally, the worst unresponsiveness I've
suffered was caused by a large dist-upgrade (over 100 packages). Things
that might go wrong are, for example, a dist-upgrade of some large
packages and an up
It's definitely not trackerd because that is not installed.
I will, however, try a clean install this evening as suggested in #131094.
--
Xubuntu Gutsy release candidate very slow
https://bugs.launchpad.net/bugs/152477
You received this bug notification because you are a member of Ubuntu
Bugs, wh
I'm changing the status to incomplete, because it has been noticed. I am
nearly sure it is a duplicate of #131094 although I'd love it if jackdaw
coould confirm it. Also changing the affected package, as it doesn't
happen with old Feisty kernel (another hint of duplicity).
** Changed in: linux-sou
lspci attached
** Attachment added: "lspci attached"
http://launchpadlibrarian.net/9974140/lspci.txt
--
Xubuntu Gutsy release candidate very slow
https://bugs.launchpad.net/bugs/152477
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubu
dmesg.log attached
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/9974112/dmesg.log
--
Xubuntu Gutsy release candidate very slow
https://bugs.launchpad.net/bugs/152477
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubun
28 matches
Mail list logo
