Sign up ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free.

I'm experiencing a really weird boot problem. With both 12.10 and 12.04LTS, the vast majority of kernels (and initrds) that I've tried boot, but hang immediately after printing out information about USB devices. This isn't exactly a full "hang" so to speak, as if I plug in a flash drive, I see information and a /dev/sd* entry printed to the screen. Post/pre-init scripts are not run, there is no handoff, nor busybox or VT prompt. Virtual terminals can't be changed (with Ctrl-Alt-Fx). For what I can see, init may have not been executed yet. With certain kernel and OS combinations however, (specifically 3.2.0-29), I get a full boot and am able to use the OS as if there is no problem. After 3.2.0-29, I've been hard pressed to find a kernel that works. Any idea what's happening or how to fix this? Or even a road to take? I've exhausted the first five pages of Google for every search term I can think of. This is a Lenovo Z580 (i5-3210M) with Phoenix SecureCore Tiano firmware, if that helps any.

share|improve this question

closed as off topic by Eliah Kagan, fabricator4, Luis Alvarado, Tom Brossman, hhlp Jan 6 '13 at 9:52

Questions on Ask Ubuntu are expected to relate to Ubuntu within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

I have the same problem with my Lenovo Ideapad Z580 and Ubuntu 12.10. My partial solution after a successfull boot is not to turn off the notebook, but using sleep mode: Fn + F1. – ferii Jan 5 '13 at 16:35
I recommend reporting this as a bug. (This question also has some good information about bug reporting.) This will probably be closed as off-topic, in accordance with the FAQ and this policy. – Eliah Kagan Jan 6 '13 at 0:31

1 Answer 1

You might try a locally-compiled kernel or another distribution, in the hopes that it's a bug related to a specific kernel configuration option. This is a bit of a long shot, though.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.