I know, that's very strange. Concerning usplash, you described this
problem well in your other bug report, this should be what usplash
developers will need to look deeper at this problem which is probably
hardware specific.
--
Can't boot after the installation of Hardy alpha 6 from Live CD only
h
The two installs that I refer to in comment 21 were both from the LiveCD
disk. One was in "try ubuntu without making changes to your system"
mode, and the second was in "install ubuntu" mode. The alternate CD had
no problem installing.
I should note, after the install from the live desktop, I did
Thanks for your comment! That sounds really strange.. I also wonder why
this happens, I don't think AFAIK that it can be fixed by any "update"
or anything like that during the installation.. the more plausible
explanation I can get is a computer failure or one of the very rare
difference between th
For better or for worse, I cannot now reproduce the problem. As the
problem was consistent (at least six or seven installs with Ubuntu
alpha5 and alpha6, and Kubuntu alpha5 and alpha 6 using the CD as a live
desktop and using the CD as install only), but now cannot be reproduced
(neither by way of
I did "sudo update-initramfs -c -a" to create (-c) new initrd images for
all (-a) kernels found in /boot. By default (without any options)
update-initramfs should update the initramfs for the newest kernel it
finds, so if the kernel you're trying to boot is the newest kernel image
you have in /boot
I'm not an expert with this, but it sounds right to me. You mount your
hard drive, you set this hard drive as root and your update the
initramfs, sounds Ok.
--
Can't boot after the installation of Hardy alpha 6 from Live CD only
https://bugs.launchpad.net/bugs/199681
You received this bug notific
I'll try to reinstall and photograph this evening. I just googled "hot to
rebuild initramfs" and came up with this:
"Boot from Livecd -> Mount drive -> Chrooted to drive -> $ update-initramfs"
Does that sound right?
So, this is what I need to do:
$ sudo mount /dev/sda1 /media/sda1
$ sudo chroot /
Okay, rebuilding initramfs for the kernel fixed it, so I guess it was
corrupted somehow.
dotancohen, could you try re-creating the initramfs for your kernel and
see if that has any effect? Also, I noticed that the messages emitted by
the kernel before getting stuck included ACPI whining about a fi
I upgraded from gutsy last night, and I get something similar. I'm not
quite sure if it's the same bug.
I think I had only the -generic kernel installed in gutsy, but the
updater seems to have installed both a new -generic kernel and a -386
one. I guess I was lucky, because the -386 kernel works b
Thanks. I haven't had the time to reinstall and post the photos, but I
know that time is running out before the release.
--
Can't boot after the installation of Hardy alpha 6 from Live CD only
https://bugs.launchpad.net/bugs/199681
You received this bug notification because you are a member of Ub
** Attachment added: "lspci.log"
http://launchpadlibrarian.net/12686344/lspci.log
--
Can't boot after the installation of Hardy alpha 6 from Live CD only
https://bugs.launchpad.net/bugs/199681
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
** Attachment added: "uname.log"
http://launchpadlibrarian.net/12686347/uname.log
--
Can't boot after the installation of Hardy alpha 6 from Live CD only
https://bugs.launchpad.net/bugs/199681
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
** Attachment added: "version.log"
http://launchpadlibrarian.net/12686348/version.log
--
Can't boot after the installation of Hardy alpha 6 from Live CD only
https://bugs.launchpad.net/bugs/199681
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I re-uploaded your logs into attached files. People from the Kernel team
needs these information to be in separate files. Since you can reproduce
this bug multiple times with the exact same result, I assign it to the
ubuntu kernel team and I set the status to confirmed.
** Changed in: linux (Ubunt
> Ok, then it means that 2) the Grub Error 15 you got is not a bug if
you did not let grub install.
Grub was working fine before the install. I specifically did not want
Ubuntu to touch Grub. So whatever happened to Grub should not have
happened, as Ubuntu should have left the working Grub alone.
15 matches
Mail list logo
