I don't see any indication of a kernel bug here, so I'm closing that
task. The bug remains open on wubi, which seems the most likely place
to look if there is still a problem.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
kernel updates get hardy boot stuck in busy box
ht
** Changed in: wubi
Status: Confirmed => Incomplete
--
kernel updates get hardy boot stuck in busy box
https://bugs.launchpad.net/bugs/236307
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
unsubscribe
On Fri, Aug 29, 2008 at 12:00 PM, Leann Ogasawara <[EMAIL PROTECTED]>
wrote:
> The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
> upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
> appreciate it if you could please test this newer 2.6.27
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
There might be several causes for busybox. A common one is that the
Windows file system has the dirty flag set, in which case you need to
clear it by booting into Windows, running chkdsk /r and rebooting
cleanly.
That said if you can boot with an older kernel (press ESC at boot after
selecting "Ub
** Also affects: wubi
Importance: Undecided
Status: New
** Changed in: wubi
Status: New => Confirmed
--
kernel updates get hardy boot stuck in busy box
https://bugs.launchpad.net/bugs/236307
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
This guy said I need to assign this bug to a package if I want action to
be taken: http://jldugger.livejournal.com/11224.html?view=14296#t14296
So, here is my best guess. Will see if anything happens...
** Changed in: linux (Ubuntu)
Sourcepackagename: None => linux
--
kernel updates get hardy
The updates have gone to -18, still the same problem, except now, an
update besides one of the old offenders:
linux-generic (2.6.24.17.19)
linux-image-2.6.24-17-generic
linux-image-generic
linux-restricted-modules-2.6.24-17-generic
linux-restricted-modules-generic
linux-ubuntu-modules-2.6.24.17-ge
I'm marking this confirmed as I can consistently reproduce this issue on
a Wubi install of Hardy. I'm still familiarizing myself with Launchpad
and, though I can't personally set the 'Importance' value, I would
suggest it be set to 'High' as it satisfies the following criteria
(taken from https://w
changing this to New so that it can be re-Confirmed following the
guidelines in https://wiki.ubuntu.com/Bugs/HowToTriage
** Changed in: ubuntu
Status: Confirmed => New
--
kernel updates get hardy boot stuck in busy box
https://bugs.launchpad.net/bugs/236307
You received this bug notificat
I might have found something useful:
by removing 'quiet splash' from the end of the 'root=...' line I was able to
look at the boot output. I was trying to determine when in the boot process
BusyBox was being invoked. The following appears in the output:
...
...
Begin: Running /scripts/local-prem
** Changed in: ubuntu
Status: New => Confirmed
--
kernel updates get hardy boot stuck in busy box
https://bugs.launchpad.net/bugs/236307
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
I guess Andrew's suggestion was a detail I left out.
When I was experiencing the busybox-syndrome, I tried a different Grub
option , but it didn't work for me. No matter which Grub option I
selected (e.g., recovery mode), I still went straight into busybox.
It wasn't that straightforward for me t
I also had this problem tonight...
Here's a temporary way for those on a Wubi install to get back to a
working system (if only until the next reboot). Pressing `Escape` right
after choosing Ubuntu from the list of available operating systems but
*before* the Ubuntu splash screen appears will prese
I also had this problem.
I salvaged my installation, but I'm still not aware of what actually solved the
problem. I'm also not sure how stable my system is now.
Here is what I did, but I can't say I figured out the cause-effect
relationship. It did lead me to the right path of a working compute
15 matches
Mail list logo
