** Changed in: linux
Importance: Unknown = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/505808
Title:
Can't boot with last linux kernels from 2.6.32.10
--
ubuntu-bugs mailing list
** Changed in: linux
Importance: High = Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/505808
Title:
Can't boot with last linux kernels from 2.6.32.10
--
ubuntu-bugs mailing list
Is this bugfix going to be backported to the kernel in lucid? Should I
ask explicitly for it?
--
Can't boot with last linux kernels from 2.6.32.10
https://bugs.launchpad.net/bugs/505808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
shankao,
The issue is identifying the fix. We've gone through many iterations of
what looked like fixes for this kernel without any success, and I
haven't seen any duplicate bugs from others encountering this issue.
Thus, I haven't been working on this bug in lieu of higher priority
issues.
If
I really love using the dev. releases and report bugs, it's the way to make
ubuntu a better S.O., and I can have it without problems on this computer, so
no need of a stable and supported release.
I'm marking the bug as fix released. Thanks Chase, it's being a pleasure to
have worked out the
Until 10.10 is released, the Maverick kernel isn't supported. Of
course, we love people who test out kernels for the next release :),
it's how we find and try to resolve bugs. But if you need official
support, we can't provide any until the kernel is officially released as
part of Ubuntu 10.10.
I'm not sure if we have understood each other this time. What I said in comment
#34 is that I have tried the new ubuntu kernel (the official one) that came in
maverick some days ago (Linux clotilde 2.6.34-2-generic #9-Ubuntu SMP Thu May
13 23:47:25 UTC 2010 i686 GNU/Linux) and it is working
@shankao:
It's generally frowned upon to use anything other than the official
release kernels. We won't be able to support you if you encounter any
other issues. That said, we have no problem with you running the kernel
as long as you understand the risks associated with it.
Unfortunately, I'm
The last kernel for maverick in the ubuntu repositories works! (Linux clotilde
2.6.34-2-generic #9-Ubuntu SMP Thu May 13 23:47:25 UTC 2010 i686 GNU/Linux)
I suppose that we can mark this bug as fixed, but, as it's the new 2.6.34 it
can still have missing some ubuntu specific patches that make it
Hi! don't worry, I suppose that finishing a release is not an easy task.
Unfortunately, that kernel still doesn't boot correctly. It keeps
showing only a black screen (doesn't show the ubuntu logo / other
graphical stuff), although I can see hard disk activity for some
moments.
I tried to change
@shankao:
I'm really sorry it's been a while since I've gotten back to you. Been
busy!
I've uploaded a new test kernel to
http://kernel.ubuntu.com/~cndougla/505808/vram2. It contains three
patches that affect the vram locations and tlb flushing. I *think* it
will resolve your issue. Please test
I have just tested two of the latest kernels in that page:
v2.6.33.3-lucid/ - Does not work. I got stuck again in a black screen.
v2.6.34-rc5-lucid/ Works and as far as I know, without any graphical
problems, neither in boot or the rest of the normal usage (I'm typing
this while using that
I have tested that patched kernel but it still doesn't boot. I tried the
radeon.modeset=0 setting with similar results.
I'm currently using an updated lucid with the last karmic kernel (as I
reinstalled karmic and updated from there).
Is there any logs or information that can we use to address
@shankao:
Can you test the latest ubuntu mainline kernel? They can be found at:
http://kernel.ubuntu.com/~kernel-ppa/mainline/
Thanks
--
Can't boot with last linux kernels from 2.6.32.10
https://bugs.launchpad.net/bugs/505808
You received this bug notification because you are a member of
There have being some advancements recently regarding this bug in
freedesktop and some patches avaliable.
Unfortunately, they seem to be only for 2.6.34 kernel. Could they be
ported back for lucid to be used?
** Summary changed:
- Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.14
+
It's been suggested in the upstream bug that this patch will fix things:
http://git.kernel.org/?p=linux/kernel/git/stable/stable-
queue.git;a=blob;f=queue-2.6.33/drm-radeon-kms-fix-rs600-tlb-
flush.patch;h=ae28c673b414ac50a93a9d4e41d35e787b0e6a94;hb=HEAD
Note that the patch is already in the
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Chase Douglas (chasedouglas)
** Changed in: linux (Ubuntu)
Status: Triaged = In Progress
--
Can't boot with last linux kernels from 2.6.32.10
https://bugs.launchpad.net/bugs/505808
You received this bug notification because you
Also, please test booting with radeon.modeset=0 on a stock kernel. Since
this patch won't get into the release image, if we find out that this
allows booting we can add it to the release note.
Thanks
--
Can't boot with last linux kernels from 2.6.32.10
https://bugs.launchpad.net/bugs/505808
You
this maybe a problem related with some mobility ati video cards. i am
also affected
--
Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.14
https://bugs.launchpad.net/bugs/505808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sure, I'm going to try the kernel in http://kernel.ubuntu.com/~kernel-
ppa/mainline/v2.6.33-rc8/ and will report any results here.
** Summary changed:
- Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.13
+ Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.14
--
Can't boot
I have tried the v2.6.33-rc8 kernel and I still get a black screen. :(
--
Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.14
https://bugs.launchpad.net/bugs/505808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
@shankao:
Unfortunately this seems to be a still present bug. You will need to
continue working with upstream through the freedesktop.org bug report to
find a resolution.
** Changed in: linux (Ubuntu)
Assignee: Chase Douglas (chasedouglas) = (unassigned)
** Changed in: linux (Ubuntu)
** Summary changed:
- Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.12
+ Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.13
--
Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.13
https://bugs.launchpad.net/bugs/505808
You received this bug notification
I made 3 tries with this kernel with mixed success:
- In the first one, I got to the login screen, but with visible
corruption (the mouse cursor is a random-dots-square, and the bottom
options are also really bad). I can login, X freeze but I can still
change to another VT.
- In the second, the
@shankao:
That's rather unfortunate. Can you try the latest mainline build of
2.6.33-rc*? If it fixes your issue, then maybe there's just a few more
patches we need. If not, then you'll likely have to comment on the
upstream bug report to try to get it resolved.
We can also look into removing
I worked with shankao through private emails to bisect to the first
commit that causes issues for him. Here's the output of the bisection
(note that the tree is the ubuntu-lucid git tree hosted at
kernel.ubuntu.com):
1369d982cea341524032a248b1f31832bb8c3eb6 is first bad commit
commit
** Bug watch added: freedesktop.org Bugzilla #25408
https://bugs.freedesktop.org/show_bug.cgi?id=25408
** Also affects: linux via
https://bugs.freedesktop.org/show_bug.cgi?id=25408
Importance: Unknown
Status: Unknown
--
Can't boot with last linux kernels from 2.6.32.10 to
** Changed in: linux
Status: Unknown = Confirmed
--
Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.12
https://bugs.launchpad.net/bugs/505808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
@shankao:
Can you test the latest kernel I've built:
http://people.canonical.com/~cndougla/505808/vram_cocktail/linux-
image-2.6.32-13-generic_2.6.32-13.19_i386.deb. It contains three new
patches:
** Changed in: linux (Ubuntu)
Status: Triaged = In Progress
--
Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.12
https://bugs.launchpad.net/bugs/505808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
@chase: em... I think that's not me...
Yes, I'm still interested in having the last kernel working. I can make some
test as you suggest, but I need some guidance. Can you please point to the info
or procedures that I should follow?
Maybe this bug report is not the better place to continue this
I am working with shankao through email to proceed with a git bisect
run. When we have results they will get posted here.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Chase Douglas (chasedouglas)
** Changed in: linux (Ubuntu)
Status: New = Triaged
--
Can't boot with last
@shankao:
Your issue seems to be related to bug 510524. Can you try upgrading your
plymouth package to see if it helps?
** Changed in: linux (Ubuntu)
Status: Triaged = Incomplete
--
Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.12
https://bugs.launchpad.net/bugs/505808
You
@Hew,
I don't think your issue is related.
--
Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.12
https://bugs.launchpad.net/bugs/505808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Upgraded to 0.8.0~-9ubuntu1 and still no change. I'm stuck with the .9
kernel :(
** Changed in: linux (Ubuntu)
Status: Incomplete = New
--
Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.12
https://bugs.launchpad.net/bugs/505808
You received this bug notification because you
@shankao:
Can you try removing plymouth and seeing if that helps?
** Changed in: linux (Ubuntu)
Status: New = Incomplete
--
Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.12
https://bugs.launchpad.net/bugs/505808
You received this bug notification because you are a member
Done, and nothing changes... but some extra complains about the missing
plymouth.
We can put plymouth out of the possible causes.
** Changed in: linux (Ubuntu)
Status: Incomplete = New
--
Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.12
@shankao:
The 2.6.32-9 kernel is based on upstream 2.6.32.1. The -10 kernel is
based on upstream 2.6.32.2. Can you try out the upstream kernels? You
can find prebuilt kernel packages at:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32.1/
I can boot with upstream 2.6.32.2
$ uname -a
Linux clotilde 2.6.32-02063202-generic #02063202 SMP Sat Dec 19 11:00:49 UTC
2009 i686 GNU/Linux
$
Do this mean that the problem is in the ubuntu changes? Should I also
test with the 2.6.32.1 one (that I can boot if ubuntu's .9 is based on
it) or
@shankao:
I think this is enough information for now. I will look into things a
bit further.
** Changed in: linux (Ubuntu)
Status: New = Triaged
** Tags removed: needs-upstream-testing
** Tags removed: i386
--
Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.12
@shankao:
There's 173 changes between the -9 and the -10 kernels. Are you able to
build and git bisect your way through a few ubuntu test kernels to
determine what change is giving you issues?
--
Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.12
** Changed in: linux (Ubuntu)
Status: Triaged = Incomplete
--
Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.12
https://bugs.launchpad.net/bugs/505808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
@shankao:
I think I just received an email from you saying your hardware has
changed and that may be making a difference for you. If this is the
case, are you still interested in following up on this issue with the
same hardware?
--
Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.12
My problem turned out to be bug 507881
--
Can't boot with last linux kernels from 2.6.32.10 to 2.6.32.12
https://bugs.launchpad.net/bugs/505808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I can't boot with 2.6.32-9-generic either. I get the following error
message which may or may not be related:
mount: mount point /proc/bus/usb does not exist
mountall: mount /proc/bus/usb [703] terminated with status 32
mountall: Filesystem could not be mounted: /proc/bus/usb
--
Can't boot
45 matches
Mail list logo
