On Fri, Dec 21, 2007 at 07:27:49AM -, Uphaar Agrawalla wrote:
It appears this bug is affecting almost everyone using Acer Aspire 4520.
The following thread has a number of users reporting the freeze-during-boot
issue:
http://ubuntuforums.org/showthread.php?t=510352page=10
Can something
It appears this bug is affecting almost everyone using Acer Aspire 4520.
The following thread has a number of users reporting the freeze-during-boot
issue:
http://ubuntuforums.org/showthread.php?t=510352page=10
Can something be done about it? It's a bit annoying, even though it
doesn't happen
Same problem with Acer 5520-5912 AMD64x2 with nVidia chipset, GeForce7000M
video.
I have tried the above solutions and nothing has helped so far. Same problem in
Gutsy RC fresh install and upgrade from feisty. Original Feisty did not have
issue, but first kernel update caused the same
Sorry, one more thing. I have installed 386 with gutsy and it works
fine. Only the Generic does not work.
--
-generic kernel doesn't boot after upgrade to Edgy prerelease (but -386 does)
https://bugs.launchpad.net/bugs/67256
You received this bug notification because you are a member of Ubuntu
sori i'm a newbie... what do you mean by changing
/dev/sda2 with /dev/mapper/something2 ...
i can't find the path /dev/mapper/ should i make one?
i'm having the same problem for my notebook ACER 4520.. and hoping to fix it
immediately...
thanks b4
--
-generic kernel doesn't boot
i solved changing /dev/sda2 with /dev/mapper/something2 both in grub and
fstab
--
-generic kernel doesn't boot after upgrade to Edgy prerelease (but -386 does)
https://bugs.launchpad.net/bugs/67256
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
it's the same with gutsy but running update-initramfs -u doesn't solve
the problem
--
-generic kernel doesn't boot after upgrade to Edgy prerelease (but -386 does)
https://bugs.launchpad.net/bugs/67256
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
This error still shows up on Gutsy Final, but now only once in a while.
When it drops me to the shell I reboot, and almost all the time it boots
properly. If it doesn't, I reboot again until it finally boots.
Please let me know if I can provide any information to help fix this.
--
-generic
Confirming this bug, it is still happening on Gutsy RC. Difference was I
did a fresh installation, so no backup kernel to fall back to. Booted
from the LiveCD, chrooted into the installation and then ran the
commands specified here followed by depmod. Finally I'm able to boot
into Ubuntu properly
sudo update-initramfs not only works for edgy... it works for feisty
fawn too!
i had the same problem over here with my 2.6.20-15-generic kernel, after
updating initramfs ($ sudo update-initramfs -u -k 2.6.20-15-generic)
everything worked fine...
i wonder why this bug still exists on feisty
--
** Changed in: initramfs-tools (Ubuntu)
Assignee: Scott James Remnant = Ubuntu Kernel Team
--
-generic kernel doesn't boot after upgrade to Edgy prerelease (but -386 does)
https://launchpad.net/bugs/67256
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Same problem here, on a AMD64 X2 3800+ / DFI nForce4 mobo
sudo update-initramfs -u -k 2.6.17-10-generic
worked like a charm, thanks for the fix
--
-generic kernel doesn't boot after upgrade to Edgy prerelease (but -386 does)
https://launchpad.net/bugs/67256
--
ubuntu-bugs mailing list
Had this problem on a dual P3/733, 256MB RAM, Compaq AP550 workstation
with Intel reference board.
I upgraded from -386 to -generic by installing the linux-kernel-generic
package and changing my grub config.
The update-initramfs method worked for me as well.
--
-generic kernel doesn't boot
Same problem here, on a [EMAIL PROTECTED]/768MB RAM/ASUS P3BF
sudo update-initramfs -u -k 2.6.17-10-generic
worked for me too.
--
-generic kernel doesn't boot after upgrade to Edgy prerelease (but -386 does)
https://launchpad.net/bugs/67256
--
ubuntu-bugs mailing list
Same problem and
sudo update-initramfs -u -k 2.6.17-10-generic
worked for me too. Thanks for the suggestion.
--
-generic kernel doesn't boot after upgrade to Edgy prerelease (but -386 does)
https://launchpad.net/bugs/67256
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I had the same problem on Edgy freshly updated from Dapper.
Booting from the i386 kernel and running sudo update-initramfs -u -k
2.6.17-10-generic solve it.
--
-generic kernel doesn't boot after upgrade to Edgy prerelease (but -386 does)
https://launchpad.net/bugs/67256
--
ubuntu-bugs mailing
Scott, this sounds like the problem you were describing last week
regarding the sort order used by update-initramfs.
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) = Scott James Remnant
--
-generic kernel doesn't boot after upgrade to Edgy prerelease (but -386 does)
Had the same problem here. Ran a combination of Frodon's and Christopher
Armstrong's scripts:
sudo update-initramfs -u -k 2.6.17-10-generic
sudo update-grub
sudo aptitude reinstall linux-restricted-modules-2.6.17-10-generic
Now everything seems to be running fine. Thank you!
--
-generic kernel
Had the same problem, the fix posted above got mine working again too.
--
-generic kernel doesn't boot after upgrade to Edgy prerelease (but -386 does)
https://launchpad.net/bugs/67256
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Just for the record and for those who have the problem, here is how i solved it
:
http://ubuntuforums.org/showthread.php?t=282956
--
-generic kernel doesn't boot after upgrade to Edgy prerelease (but -386 does)
https://launchpad.net/bugs/67256
--
ubuntu-bugs mailing list
I ran into this problem as well, and Froden's steps worked for me,
except I had to manually run 'depmod' before I rebooted or I got:
FATAL: Could not load /lib/modules/2.6.17-10-generic/modules.dep: No
such file or directory
--
-generic kernel doesn't boot after upgrade to Edgy prerelease (but
Same problem here.
But sudo update-initramfs -u -k 2.6.17-10-generic don't help because the
initramfs script don't even seem to exist for me.
You may need (like me) to create it before running the sudo update-initramfs
-u -k 2.6.17-10-generic command :
sudo mkinitramfs -o
Ok, here it is. The file is brand new as of Thursday, and that's when it
was last modified: Thursday was when I upgraded to edgy using update-
manager.
** Attachment added: initrd that doesn't boot
http://librarian.launchpad.net/4921339/initrd.img-2.6.17-10-generic
--
-generic kernel doesn't
** Changed in: Ubuntu
Sourcepackagename: None = linux-source-2.6.17
--
-generic kernel doesn't boot after upgrade to Edgy prerelease (but -386 does)
https://launchpad.net/bugs/67256
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Thanks for allocating this appropriately.
So, I fixed the booting problem with the following command:
sudo update-initramfs -u -k 2.6.17-10-generic
I'm not sure what this implies. I made a backup of the previous initrd
image in case it would be useful for the bug report. Just say the word
and I
Please go ahead and attach the problematic initrd.gz to this bug report.
Thanks
** Changed in: linux-source-2.6.17 (Ubuntu)
Sourcepackagename: linux-source-2.6.17 = initramfs-tools
--
-generic kernel doesn't boot after upgrade to Edgy prerelease (but -386 does)
https://launchpad.net/bugs/67256
26 matches
Mail list logo
