Karmic Koala stops dead after /scripts/init-bottom

[Ivan Wills]

Hi,

After an update yesterday my Karmic installation no longer completely boots in any kernel (in safe or other wise) I have kernels 2.30.8, 2.30.9 and 2.30.10 installed.

When not in safe mode I see the splash screen the the screen goes blank and nothing happens. I can press Alt-F1 and what I see something like the following:

kinit: name_to_dev_t(/dev/disk/by-uuid/...) - dev(8,3)
kinit: trying to resume from /dev/disk/by0uuid/...
kinit: No resume image, doing normal boot...

In safe mode I see the above with the following additional lines:

Begin: Running /scripts/local-bottom ...
Done.
Done.
Begin: Running /scripts/init-bottom ...
Done.
[ 42.560077] CE: hpet increasing min_delta_ns to 15000 nsec

Immediately after updating X appeared to have died but I could access virtual terminals now after attempting to reboot (with all kernels) I never get any virtual terminals.

Regards,
Ivan Wills

[Chatur Ratna Shakya (chatur)]

Hi,

I'm having same problem here. I there any way around.

Regards,

Chatur

[MiK (kimlop)]

hi, i have the same problem

I tried to boot with different kernel, but the system not boot

[rabbitear (weatchu)]

Same thing happened to me.

The fix (hack) how I got it to but was (boot another way CD, etc), goto the /etc/init/ directory and you'll see everything has .dpkg-new extentions.. take those extentions off of all files in that directory and reboot that harddrive again.

I also got rid of the UUID's in fstabs (replaced back to there device name) but that probably didn't have to be done.

j.

[Leonty (leonty)]

I confirm this issue. I did upgrading from kubuntu 9.04 to 9.10 alpha and at some point when setting up downloaded packaged the system just freezed reacting only to the power button pressed for 6 sec.
Consequent reboots (doesn't matter if the recovery kernel was used or not) freezed the same way after the line:

Begin: Running /scripts/init-bottom ...
Done.

I also blamed a line like "Clocksource tsc unstable (delta = -127665427 ns)" right after the lines above but adding "notsc" parameter to the kernel eliminated the warning and kept freezes.
The fix in the message #3 rabbitear helped (though I didn't touch fstab).

[entertain (v-admin-faq4pcs-de)]

same issue here.

I want to boot my ubuntu. I'm missing it so much. :(

[rabbitear (weatchu)]

I'll try to write my email alittle bit more clear, atleast my Hack to that
specific issue: (because now I've switched to Arch, and it is probably a bad
excussion):

You could do it two ways. One is boot from a usbkey, live version, or a cd,
knoppix or anything that you can get your console on the machine and mount
drives works fine.

You mount your drive, goto the "etc/init" directory and rename those files
(all of them) so they do not have the .dpkg-new extention, just the original
name.

If you mounted your ROOT onto /mnt, you would be looking in /mnt/etc/init

thats all, the way I did it was to use the boot option 'init=/bin/bash' (via
grub or lilo etc) because I didn't have a usbkey or cdrom drive. In that
case you are already on your on ROOT.

j.

On Mon, Aug 24, 2009 at 4:06 PM, entertain <email address hidden> wrote:

> same issue here.
>
> I want to boot my ubuntu. I'm missing it so much. :(
>
> --
> Karmic Koala stopps dead after /scripts/init-bottom
> https://bugs.launchpad.net/bugs/398214
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Ubuntu: New
>
> Bug description:
> Hi,
>
> After an update yesterday my Karmic installation no longer completely boots
> in any kernel (in safe or other wise) I have kernels 2.30.8, 2.30.9 and
> 2.30.10 installed.
>
> When not in safe mode I see the splash screen the the screen goes blank and
> nothing happens. I can press Alt-F1 and what I see something like the
> following:
>
> kinit: name_to_dev_t(/dev/disk/by-uuid/...) - dev(8,3)
> kinit: trying to resume from /dev/disk/by0uuid/...
> kinit: No resume image, doing normal boot...
>
> In safe mode I see the above with the following additional lines:
>
> Begin: Running /scripts/local-bottom ...
> Done.
> Done.
> Begin: Running /scripts/init-bottom ...
> Done.
> [ 42.560077] CE: hpet increasing min_delta_ns to 15000 nsec
>
> Immediately after updating X appeared to have died but I could access
> virtual terminals now after attempting to reboot (with all kernels) I never
> get any virtual terminals.
>
> Regards,
> Ivan Wills
>

[Bart Broeckx (bart)]

Same problem here, have to boot in Hardy again because Karmic doesn't show a GNOME interface anymore.

[Bart Broeckx (bart)]

The solution in #3 doesn't seem to work for me. There are no files with .dpkg-new extensions in the /etc/init/ directory.
All files have a .conf extension like rc.conf or tty3.conf

Sorry if I overlooked something and made a fool out of myself.

[rabbitear (weatchu)]

Well, the *.dpkg-new files themselves will be always (not to everything, but
to anything where the /etc/* is new and different) be put there.

So, any time you may "quit" an upgrade in the middle, you probably will have
those. I don't recall myself quiting a dist-upgrade before (maybe I did
maybe I didn't, so I am now trying to talk about Karmic). What I'm getting
at is that IF, "it" (the Karmic upgrade stopping) replaces /etc files that
are critical, with the "conf".dpkg-new's, AND is erasing the "conf" etc, AND
they are needed to boot, or start X or anything else.. As you can see, the
system is looking for the "confs" and can not find them. So it fails.

That was MY issue, I am not that much in the debian/ubuntu loop, just have
been using them for awhile.

All other issues are possible. If it was a similar issue of this type, I
would need to guess that some other critical "confs" have been changed,
adding the extention of .dpkg-new (which is normal) AND deleting the old
"conf" at the same time.

I really don't know much about what "apt" is actually suppose to be doing
under the hood.

Like I say, any issue is possible, but maybe (this may or may not help) read
log files, all of them, just after boot, and failing.

jon.

On Wed, Aug 26, 2009 at 6:44 AM, bartek <email address hidden> wrote:

> The solution in #3 doesn't seem to work for me. There are no files with
> .dpkg-new extensions in the /etc/init/ directory.
> All files have a .conf extension like rc.conf or tty3.conf
>
> Sorry if I overlooked something and made a fool out of myself.
>
> --
> Karmic Koala stopps dead after /scripts/init-bottom
> https://bugs.launchpad.net/bugs/398214
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Ubuntu: New
>
> Bug description:
> Hi,
>
> After an update yesterday my Karmic installation no longer completely boots
> in any kernel (in safe or other wise) I have kernels 2.30.8, 2.30.9 and
> 2.30.10 installed.
>
> When not in safe mode I see the splash screen the the screen goes blank and
> nothing happens. I can press Alt-F1 and what I see something like the
> following:
>
> kinit: name_to_dev_t(/dev/disk/by-uuid/...) - dev(8,3)
> kinit: trying to resume from /dev/disk/by0uuid/...
> kinit: No resume image, doing normal boot...
>
> In safe mode I see the above with the following additional lines:
>
> Begin: Running /scripts/local-bottom ...
> Done.
> Done.
> Begin: Running /scripts/init-bottom ...
> Done.
> [ 42.560077] CE: hpet increasing min_delta_ns to 15000 nsec
>
> Immediately after updating X appeared to have died but I could access
> virtual terminals now after attempting to reboot (with all kernels) I never
> get any virtual terminals.
>
> Regards,
> Ivan Wills
>

[MT (micdhack)]

i just did a dist-upgrade on karmic and i have the problem.
The solution above does not work.

I found out that if you use through group the init=/bin/bash and change the ro option to rw you can have some short of a console to work with the filesystem.
When i tried to upgrade i had the error that initscripts have been kept back and if i would try to force install then i have to lose all xorg packages!

[MT (micdhack)]

My problem was fixed after normal upgrade

[AnthonyC (capone)]

Yeah, having the same problem too. I did was the update manager suggested, a partial upgrade... then rebooted... now, I can't get Gnome back! arrr...missing NBR!

Seems like the update manager held two packages back, the upstart and initscripts.

Don't know what you mean by "fixed after normal upgrade"...but I sure would like to get my Karmic NBR back!

I checked the above solutions... don't have any of the suggested files sitting in /etc/init

Anyone?

[rabbitear (weatchu)]

well "my solution" wouldn't be an absolute one as I was saying, again, I'll
tell you it looks like the /etc/ files are being mv'd to the *.dpkg-new, and
WITHOUT ANY of the '/etc' file, WHATEVER IT IS xorg, init etc. That
"system" xorg, init, etc. will not work.

So, where ever your upgrade stops, meaning it was stopped at any point in
time in the upgrade, which means it was a different "system" xorg, init,
etc, things that you would notice on your system not booting. There is a
/etc file missing.

to summery THERE IS NO CONFIGURATION ANYMORE in that specific "system".

It seems to rename them, so that hacked up fix would to to rename them back.
That is all.

--------------------
by the word "system": X windows, Init scripts, Gnome, (well gnome is over X,
remember that too) .. This bug is about "Quitting the upgrade premature,
then you notice it doesn't boot" --- other things (to this effect, say you
don't have a syslog) could actually happen.

I'm just trying to describe and define it here.
not offer the "right" fix, thats for the ubuntu guys :)

peace.

On Tue, Sep 15, 2009 at 2:33 PM, AnthonyC <email address hidden> wrote:

> Yeah, having the same problem too. I did was the update manager
> suggested, a partial upgrade... then rebooted... now, I can't get Gnome
> back! arrr...missing NBR!
>
> Seems like the update manager held two packages back, the upstart and
> initscripts.
>
> Don't know what you mean by "fixed after normal upgrade"...but I sure
> would like to get my Karmic NBR back!
>
> I checked the above solutions... don't have any of the suggested files
> sitting in /etc/init
>
> Anyone?
>
> --
> Karmic Koala stopps dead after /scripts/init-bottom
> https://bugs.launchpad.net/bugs/398214
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Ubuntu: New
>
> Bug description:
> Hi,
>
> After an update yesterday my Karmic installation no longer completely boots
> in any kernel (in safe or other wise) I have kernels 2.30.8, 2.30.9 and
> 2.30.10 installed.
>
> When not in safe mode I see the splash screen the the screen goes blank and
> nothing happens. I can press Alt-F1 and what I see something like the
> following:
>
> kinit: name_to_dev_t(/dev/disk/by-uuid/...) - dev(8,3)
> kinit: trying to resume from /dev/disk/by0uuid/...
> kinit: No resume image, doing normal boot...
>
> In safe mode I see the above with the following additional lines:
>
> Begin: Running /scripts/local-bottom ...
> Done.
> Done.
> Begin: Running /scripts/init-bottom ...
> Done.
> [ 42.560077] CE: hpet increasing min_delta_ns to 15000 nsec
>
> Immediately after updating X appeared to have died but I could access
> virtual terminals now after attempting to reboot (with all kernels) I never
> get any virtual terminals.
>
> Regards,
> Ivan Wills
>

[rabbitear (weatchu)]

You could make a quick dirty "script" to fix it, I usually would do that
manually, but it WILL mess up anything else in the /etc/ that you changed
for your purposes.

but what your doing would be:

finding all files in /etc
if the file has *.dpkg-new
cp that to just *

Any compiled package has the specific file name/path of the "config" it
needs to start up, it doesn't want config.dpkg-new. You can see that it is
a different file name yourself.
ubuntu's karmic install doesn't take into account that you will quit in the
middle.
jon.

On Tue, Sep 15, 2009 at 5:11 PM, Jon Bradley <email address hidden> wrote:

> well "my solution" wouldn't be an absolute one as I was saying, again, I'll
> tell you it looks like the /etc/ files are being mv'd to the *.dpkg-new, and
> WITHOUT ANY of the '/etc' file, WHATEVER IT IS xorg, init etc. That
> "system" xorg, init, etc. will not work.
>
> So, where ever your upgrade stops, meaning it was stopped at any point in
> time in the upgrade, which means it was a different "system" xorg, init,
> etc, things that you would notice on your system not booting. There is a
> /etc file missing.
>
> to summery THERE IS NO CONFIGURATION ANYMORE in that specific "system".
>
> It seems to rename them, so that hacked up fix would to to rename them
> back.
> That is all.
>
> --------------------
> by the word "system": X windows, Init scripts, Gnome, (well gnome is over
> X, remember that too) .. This bug is about "Quitting the upgrade premature,
> then you notice it doesn't boot" --- other things (to this effect, say you
> don't have a syslog) could actually happen.
>
> I'm just trying to describe and define it here.
> not offer the "right" fix, thats for the ubuntu guys :)
>
> peace.
>
>
>
> On Tue, Sep 15, 2009 at 2:33 PM, AnthonyC <email address hidden> wrote:
>
>> Yeah, having the same problem too. I did was the update manager
>> suggested, a partial upgrade... then rebooted... now, I can't get Gnome
>> back! arrr...missing NBR!
>>
>> Seems like the update manager held two packages back, the upstart and
>> initscripts.
>>
>> Don't know what you mean by "fixed after normal upgrade"...but I sure
>> would like to get my Karmic NBR back!
>>
>> I checked the above solutions... don't have any of the suggested files
>> sitting in /etc/init
>>
>> Anyone?
>>
>> --
>> Karmic Koala stopps dead after /scripts/init-bottom
>> https://bugs.launchpad.net/bugs/398214
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>> Status in Ubuntu: New
>>
>> Bug description:
>> Hi,
>>
>> After an update yesterday my Karmic installation no longer completely
>> boots in any kernel (in safe or other wise) I have kernels 2.30.8, 2.30.9
>> and 2.30.10 installed.
>>
>> When not in safe mode I see the splash screen the the screen goes blank
>> and nothing happens. I can press Alt-F1 and what I see something like the
>> following:
>>
>> kinit: name_to_dev_t(/dev/disk/by-uuid/...) - dev(8,3)
>> kinit: trying to resume from /dev/disk/by0uuid/...
>> kinit: No resume image, doing normal boot...
>>
>> In safe mode I see the above with the following additional lines:
>>
>> Begin: Running /scripts/local-bottom ...
>> Done.
>> ...

[chisao (michayc)]

I also have this problem.I m running kubuntu 9.10 alpha 5 on asus eeepc 1000H.I tried the above fix but it's not workin for me because all my files in the /etc/init ends in .conf.This happened after an update yesterday.I did the update, played around for some time then I shut it down and tonight this happened.

[Khairul Aizat Kamarudzzaman (fenris)]

same goes to me .. the fix doesn't work for me ... :( i can't boot into my ubuntu :( ... home someone may triage this bug a.s.a.p and have solution / fix for it ...

[Colin Watson (cjwatson)]

rabbitear: The presence of .dpkg-new files implies (and has always implied, since well before Ubuntu even existed) that the package owning them has not been properly configured. Try 'sudo dpkg --configure -a'.

[Khairul Aizat Kamarudzzaman (fenris)]

colin,

is there any otherway to boot it / fix it ? or using live CD?

[Khairul Aizat Kamarudzzaman (fenris)]

Hi Guys,

I currently has solve this issue by booting the Ubuntu server then use the Rescue Mode, choose your root partition then do update and dist-upgrade ..

Now Im in Alpha6 .. surviving from this bugs :)

[chisao (michayc)]

I fixed it somehow...Many steps and I don't know if I remember them all.First...press e on recovery to edit.change ro single to rw init=/bin/bash.Then type dhclient eth0 (connect an ethernet cable first if you havent already).If it manages to connect (which it should) type aptitude update and then aptitude upgrade.It will update (mine failed a few packages because something was not mounted...I dont know exactly what happened).After this I tried to boot using the latest kernel but it froze sayin somethin about kernel panic......initramfs....vsync....I dont remember exactly.Anyway I chose the previous kernel in recovery mode run fsck, rebooted again with the previous kernel in recovery and the options were there.I chose make free space then fsck and then resume normal boot and I got in kde.I ran aptitude again aptitude autoremove apt-get autoclean apt-get autoremove aptitude update aptitude upgrade and all that stuff...rebooted with new kernel and after a few messages I got in....Hope it helps.

[Paul (slize)]

Thank you chisao, you saved my night!

Here is what I did:

1. Ensure you are connected to your router by DHCP.
2. Start your machine and select the "recovery kernel linux 2.6.31-10" with the "down" button. Press "e" on your keyboard.
3. Select the "kernel uuid=..." entry with the "down" button and type "e" again.
4. Change "ro single" to "rw init=/bin/bash". Press "Enter" and "b" on the keyboard.
5. Wait until booting stops and press "Enter".
6. "root@(none):" is displayed. Type in the konsole:
dhclient eth0
7. After this operation the connection to the internet is activated and you can type in the konsole:
apt-get dist-upgrade
8. Wait 10 min until upgrade is done.
9. Reboot your machine and select "kernel linux 2.6.31-9" in grub.

Ubuntu works.

I tried to start "kernel linux 2.6.31-10" after the upgrade but this didn´t work. Probably the next dist-upgrade does it.

[rabbitear (weatchu)]

Let me remind you fools, that the stuff your saying, is just another 'bug'
it ain't solved like this...

you will know that.

On Thu, Sep 17, 2009 at 5:31 PM, Paul <email address hidden> wrote:

> Thank you chisao, you saved my night!
>
> Here is what I did:
>
> 1. Ensure you are connected to your router by DHCP.
> 2. Start your machine and select the "recovery kernel linux 2.6.31-10" with
> the "down" button. Press "e" on your keyboard.
> 3. Select the "kernel uuid=..." entry with the "down" button and type "e"
> again.
> 4. Change "ro single" to "rw init=/bin/bash". Press "Enter" and "b" on the
> keyboard.
> 5. Wait until booting stops and press "Enter".
> 6. "root@(none):" is displayed. Type in the konsole:
> dhclient eth0
> 7. After this operation the connection to the internet is activated and you
> can type in the konsole:
> apt-get dist-upgrade
> 8. Wait 10 min until upgrade is done.
> 9. Reboot your machine and select "kernel linux 2.6.31-9" in grub.
>
> Ubuntu works.
>
> I tried to start "kernel linux 2.6.31-10" after the upgrade but this
> didn´t work. Probably the next dist-upgrade does it.
>
> --
> Karmic Koala stopps dead after /scripts/init-bottom
> https://bugs.launchpad.net/bugs/398214
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Ubuntu: New
>
> Bug description:
> Hi,
>
> After an update yesterday my Karmic installation no longer completely boots
> in any kernel (in safe or other wise) I have kernels 2.30.8, 2.30.9 and
> 2.30.10 installed.
>
> When not in safe mode I see the splash screen the the screen goes blank and
> nothing happens. I can press Alt-F1 and what I see something like the
> following:
>
> kinit: name_to_dev_t(/dev/disk/by-uuid/...) - dev(8,3)
> kinit: trying to resume from /dev/disk/by0uuid/...
> kinit: No resume image, doing normal boot...
>
> In safe mode I see the above with the following additional lines:
>
> Begin: Running /scripts/local-bottom ...
> Done.
> Done.
> Begin: Running /scripts/init-bottom ...
> Done.
> [ 42.560077] CE: hpet increasing min_delta_ns to 15000 nsec
>
> Immediately after updating X appeared to have died but I could access
> virtual terminals now after attempting to reboot (with all kernels) I never
> get any virtual terminals.
>
> Regards,
> Ivan Wills
>

[Paul (slize)]

Thank you for reminding me. Sometimes I forget my foolishness.

[rabbitear (weatchu)]

hey, foolishness == bugzilla state.
no problem.

On Thu, Sep 17, 2009 at 6:20 PM, Paul <email address hidden> wrote:

> Thank you for reminding me. Sometimes I forget my foolishness.
>
> --
> Karmic Koala stopps dead after /scripts/init-bottom
> https://bugs.launchpad.net/bugs/398214
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Ubuntu: New
>
> Bug description:
> Hi,
>
> After an update yesterday my Karmic installation no longer completely boots
> in any kernel (in safe or other wise) I have kernels 2.30.8, 2.30.9 and
> 2.30.10 installed.
>
> When not in safe mode I see the splash screen the the screen goes blank and
> nothing happens. I can press Alt-F1 and what I see something like the
> following:
>
> kinit: name_to_dev_t(/dev/disk/by-uuid/...) - dev(8,3)
> kinit: trying to resume from /dev/disk/by0uuid/...
> kinit: No resume image, doing normal boot...
>
> In safe mode I see the above with the following additional lines:
>
> Begin: Running /scripts/local-bottom ...
> Done.
> Done.
> Begin: Running /scripts/init-bottom ...
> Done.
> [ 42.560077] CE: hpet increasing min_delta_ns to 15000 nsec
>
> Immediately after updating X appeared to have died but I could access
> virtual terminals now after attempting to reboot (with all kernels) I never
> get any virtual terminals.
>
> Regards,
> Ivan Wills
>

[Paul (slize)]

Hi,

try "nomodeset" parameter during boot:

1. Start your machine and select the "kernel linux" with the "down" button.
2. Press "e" on your keyboard.
3. Select the "kernel uuid=..." entry with the "down" button and type "e" again.
4. Change "quite splash" to "nomodeset". Press "Enter" and "b" on the keyboard.

[Leonard Broman (firepiper)]

I just tried to upgrade to the RC and I got a similar problem. My disks do not mount anymore. The system seems to recognise my disks but not the partitions anymore. I'm left at the busybox console and there are no drives under /dev/disks/by-uuid/. Maybe theres a more specific bug for my case if anyones seen it?

Unfortunately I'm away until tomorrow, but if this is a problem with the release candidate as well, I think it's quite alarming.

Is anyone prepared to escalate this issue?

[Paul van Genderen (paulvg)]

This happens on all my Xen domU's, my test environment is now dead.

Here are perfectly reproducible steps to trigger this bug:

1. xen-create-image --verbose --hostname domx.example.net --ip=192.168.1.x --dist=intrepid
2. once it's up, ssh into it
3. apt-get --no-install-recommends update-manager-core
4. do-release-upgrade
5. follow the steps (answer y on everything)
6. once it's rebooted, ssh back in, it's running 9.04 now
7. do-release-upgrade

[Kasimir Gabert (kasimir-g)]

I can confirm that this problems occurs with a fresh install of Karmic under Xen. Does anybody have a good way of getting around this? I am running Xen 3.2 on Debian Lenny.

[Scott James Remnant (Canonical) (canonical-scott)]

No evidence that this is an Upstart issue, try adding "--verbose" to the kernel command-line - what output do you get then?

[Julian Davison (julian-bugs)]

Console output from a Xen machine useful?

[JimPBarber (jim-barbergroup)]

chisao and paul rock!!

Thank you. This worked like a charm. I was able to recover in just a couple of minutes. I then used update manager to install the missing pieces.

Thanks again!

[Berteun (berteun)]

I can confirm the behaviour. I made a Xen DomU for karmic under lenny, using lenny's kernel (Debian xen kernel 2.6.26-2-xen-amd64). After init-bottom it drops dead. I also tried to upgrade from a working Ubuntu jaunty install (image from http://stacklet.com/downloads/images/lister/Ubuntu/9.04/x86-64 ) – the 9.04 worked (I have log too if someone cares), the 9.10 does not. I first thought that maybe the hwclock script was the culprit, xen removes this normally, so I removed it too but it didn't help. The last lines when providing --verbose are:

init: mountall state changed from spawned to post-start
init: mountall state changed from post-start to running
init: Handling started event
init: Handling mount event

And then it stops using 100% CPU according to xen top.

[Berteun (berteun)]

Some further investigation shows that for me the problem occurs when the mountall process is executed, as described here: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/469985

[Berteun (berteun)]

For those using karmic under Xen 3.2: the Debian 2.6.26 kernel is too old – I made a comment on https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/469985 – and it misses pipe2, which causes mountall to loop indefenitely and hence the bootup fails.

[panticz.de (panticz.de)]

Hi, the default Ubuntu kernel from Karmic includes support for Xen domU. You have to copy the Kermic kernel to your Dom0 and make some changes on the VM config file, see my HowTo: http://www.panticz.de/Ubuntu-Karmic-domU-under-Debian-Lenny-Dom0 then you can start your VM.

Best Regards

panticz

[rabbitear (weatchu)]

the Root of the problem is that FILES in /etc are mv'd (moved) to *.dpkg-new

So they are not there upon reboot.

Just a reminder..

j.

On Tue, Nov 24, 2009 at 5:28 AM, panticz.de <email address hidden> wrote:

> Hi, the default Ubuntu kernel from Karmic includes support for Xen domU.
> You have to copy the Kermic kernel to your Dom0 and make some changes on
> the VM config file, see my HowTo: http://www.panticz.de/Ubuntu-Karmic-
> domU-under-Debian-Lenny-Dom0<http://www.panticz.de/Ubuntu-Karmic-%0AdomU-under-Debian-Lenny-Dom0>then you can start your VM.
>
> Best Regards
>
> panticz
>
> --
> Karmic Koala stops dead after /scripts/init-bottom
> https://bugs.launchpad.net/bugs/398214
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Ubuntu: Incomplete
>
> Bug description:
> Hi,
>
> After an update yesterday my Karmic installation no longer completely boots
> in any kernel (in safe or other wise) I have kernels 2.30.8, 2.30.9 and
> 2.30.10 installed.
>
> When not in safe mode I see the splash screen the the screen goes blank and
> nothing happens. I can press Alt-F1 and what I see something like the
> following:
>
> kinit: name_to_dev_t(/dev/disk/by-uuid/...) - dev(8,3)
> kinit: trying to resume from /dev/disk/by0uuid/...
> kinit: No resume image, doing normal boot...
>
> In safe mode I see the above with the following additional lines:
>
> Begin: Running /scripts/local-bottom ...
> Done.
> Done.
> Begin: Running /scripts/init-bottom ...
> Done.
> [ 42.560077] CE: hpet increasing min_delta_ns to 15000 nsec
>
> Immediately after updating X appeared to have died but I could access
> virtual terminals now after attempting to reboot (with all kernels) I never
> get any virtual terminals.
>
> Regards,
> Ivan Wills
>

[Cocodude (marc-indivisibilities)]

Confirmed the issue that panticz.de saw here when using Debian Lenny with a Ubuntu 9.10 domU. The kernel does indeed need to be upgraded and I had luck using the OpenSuSE 2.6.27 kernel.

[rabbitear (weatchu)]

LinkedIn
------------

Bug,

I'd like to add you to my professional network on LinkedIn.

- Jon Bradley

Jon Bradley
Student at University of Alaska Anchorage
Anchorage, Alaska Area

Confirm that you know Jon Bradley
https://www.linkedin.com/e/isd/1285280660/fLA6AFK3/

------
(c) 2010, LinkedIn Corporation

[saewelo (saewelo1)]

I am still experiencing this issue on kernel 2.6.32-24. It seems completely random. Most times when my net-book hangs (Compaq 110C-1100CA) after the /scripts/init-bottom... I can power off/on and it will boot normally on the second attempt. I thought it may have something to do with AHCI but I do not have the ability to set the mode to "compatible" in my BIOS.

Is there a way I can "switch off" AHCI in the kernel to test?

[Launchpad Janitor (janitor)]

[Expired for Ubuntu because there has been no activity for 60 days.]

[Richard Midwinter (rich-midwinter)]

I had this today. Couldn't spot any dpkg.new files in /etc but dpkg --configure -a fixed enough for a normal kernel to boot to a sensible prompt.