I have the same problem with my Intel PRO/Wireless 2200BG in a VAIO VNG-S4HP!
He worked fine for the last 6 months (including after I upgrade to 9.04), until
last week, when he disconnected from my network while I was using Firefox. Now
he “connects” but no Internet (when I ping my router I rece
I have the same problem... I kind of "solve" it by pressing e (when the
system shows the menu with several kernel possibilities) and editing the
file, making only the following change: where is "2.6.31-15-generic"
write "2.6.31-14-generic" (loads the older kernel). Press Ctr x and you
should be abl
Response to #84: In the beginning of this problem I didn't have any
menu at startup, the system when to the grub prompt! After following the
procedure in #82 (using kernel version ...-15) I got a menu, but I
wasn't able to boot (I got the kernel panic thing). The only way to boot
it is explained i
Here it goes...
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s /boot/grub/grubenv ]; then
have_grubenv=true
load_env
fi
set default="0"
Now this is weird... I had to install some programs and now, when I boot
the system, the grub menu is gone! I only get the grub prompt, but I am
able to boot manually using:
>linux /boot/vmlinuz-2.6.31-14-generic root=/dev/sda1
>loop=/ubuntu/disks/root.disk ro single
>initrd /boot/initrd.img-2.6.
The problem is now identified, grub2 in some cases recognizes loop0 as
an ext2 when is an ext4 (and so it is unable to read it properly)! But
is strange how it is taken so much time to find a solution... So stay
with #145 or #149 and wait.
--
Wubi/Karmic boot: kernel panic - not synching: VFS
ht
*** This bug is a duplicate of bug 477169 ***
https://bugs.launchpad.net/bugs/477169
This bug is related with https://bugs.launchpad.net/wubi/+bug/477169,
and you should follow the discussion there.
--
[karmic] Grub Menu Lost, need to manually mount virtual disk
https://bugs.launchpad.net/bu
Dear Fellows YOU ARE WASTING YOUR TIME by deleting kernels, reinstalling
grub or wubi... and confusing the people with less experience. The
problem has been identified (see #154) an SEVERAL WORKAROUNDS have been
found... .
[IF YOU DON'T KNOW HOW TO BOOT MANUALLY IN UBUNTU see #145]
WORKAROUND - 1
give it a try and don't do nothing... reboot and if all goes well
something has (finally) done his work and you can forget this thing, if
not you must redo the all thing.
WORKAROUND - 2 (read the entries of Mark Abene).
--
Wubi/Karmic boot: kernel panic - not synching: VFS
https://bugs.launchpad
jrd... look to #160 for an improved solution that uses the new kernels
(as a said above, the problem is not with the new kernels)! And if
ubuntu keeps with the same process of the last kernel updates, the
directory ubuntu/install/boot/grub will be updated or the files will be
deleted in the new up
At least part of the problem is that grub cannot read text files coded
in UTF8! I am able to boot from a grub.cfg file from another partition
coded in ANSI, but if I change that file to UTF8, grub is not able to
read it.
--
Wubi/Karmic boot: kernel panic - not synching: VFS
https://bugs.launchpad
I am sorry but the conclusion of my last entry is wrong! What we can
conclude is that grub is not seeing the content of the files, try cat
(loop0)/boot/grub/grub.cfg, in my case it showed the content of some
openoffice file! I tried cat with several files, some seem ok, but
other are completely wr
Mark... You are not helping, you are bulling people. Go away and cool
down! If you want to help, find a proper solution because, for now, your
"solution" sucks...
--
Wubi/Karmic boot: kernel panic - not synching: VFS
https://bugs.launchpad.net/bugs/477169
You received this bug notification becaus
HOWTO: a "workaround" (before a really fix to this bug is found)
FOR PEOPLE WHO ARE ABLE TO BOOT UBUNTU MANUALLY (see bellow)*
(1) Boot ubuntu manually and copy the file /boot/grub/grub.cfg to a pen
(2) Edit the file (in the pen) with a text editor and delete the menuentry for
kernel -16 and -1
Yes, you must do step (6) to find out where windows is...
--
Wubi/Karmic boot: kernel panic - not synching: VFS
https://bugs.launchpad.net/bugs/477169
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
#137 ... that it is only true in some installations... but you are
right, for most of the cases you can do as in #137. Anyway, I advise to
put grub.cfg in the root of the windows system partition (usually c:\).
--
Wubi/Karmic boot: kernel panic - not synching: VFS
https://bugs.launchpad.net/bugs/
If all kernels become unbootable and you don't have a initrd for your
system, then you are in a deep sh... that is why I advise to copy it to
c:\. But you can use Live CD to access your files in the root.disk.This
is how:
Boot from the Live CD and at a terminal prompt, enter:
(1) sudo mkdir /win
(
It isn't a problem of corruption...
These files are "compiled" when the system installs a new kernel or you
enter an update-grub command. It seems (?) that initrd* is not "properly
compiled" but grub.cfg is... anyway when the system restarts, grub
doesn't find the content of these files [you can s
-- A RECAP --
HOWTO: a "workaround" (before a really fix to this bug is found)
(1) Boot ubuntu manually [FOR PEOPLE WHO ARE NOT ABLE TO BOOT UBUNTU MANUALLY
(see bellow)*]
(2) Check if /host is your windows directory (use Nautilus (the file manager!)
and see)
meow81 #144... Yes you can backup all these files.
--
Wubi/Karmic boot: kernel panic - not synching: VFS
https://bugs.launchpad.net/bugs/477169
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
Because grub was able to "figured out" that information, but in general
you have to indicate grub that info for proper handling of the disks.
--
Wubi/Karmic boot: kernel panic - not synching: VFS
https://bugs.launchpad.net/bugs/477169
You received this bug notification because you are a member of
A SIMPLER "SOLUTION":
Enter at terminal:
(1) sudo update-grub
(2) sudo cp -r /boot /host
(3) nano /host/boot/grub/grub.cfg
(and change the line initrd /boot/initrd.img-2.6.31-16-generic to initrd
(hd0,1)/boot/initrd.img-2.6.31-16-generic [adapt to your case (h0,1) should be
(hd0,2) in many ca
Mark, WHERE is the solution for this problem, in the case Wubi, Grub 2
and kernel...-15-...? Please!
For now, I am able to boot, using kernel-14, by choosing that option in
the grub menu at startup. Sometimes this menu don't show up (why? I
don't know!) and I follow #91 and then I enter "sudo upd
smallbob ...
Did you tried:
>linux /boot/vmlinuz-2.6.31-14-generic root=/dev/sda5
>loop=/ubuntu/disks/root.disk ro quiet splash
>initrd /boot/initrd.img-2.6.31-14-generic
>boot
Please check if the boot partion is sda5...? It could be sda1 (just
try again with other number!).
Read #9
smallbob...
I am sorry that this didn't work! For me it worked in 3 different
computers... maybe the situation is not the same. You should try the
Mark Abene "solution".
However you can access your files using the process described in
[https://wiki.ubuntu.com/WubiGuide#How can I access the Wubi f
25 matches
Mail list logo
