Does "update-initramfs -k all -u" followed by a reboot make it boot
successfully into the 2.6.22 kernel? If so, this is a duplicate of
149565.
** Changed in: linux-source-2.6.22 (Ubuntu)
Sourcepackagename: None => linux-source-2.6.22
--
will not boot 2.6.22-** linux image
https://bugs.launchpad.
I just ran "update-initramfs -k all -u" and know no image will boot.
--
will not boot 2.6.22-** linux image
https://bugs.launchpad.net/bugs/151132
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
** Description changed:
- When I get right passed the bios screen before I get to the Ubuntu
- splash I get the following message:
+ When I get right pass the bios screen before I get to the Ubuntu splash
+ I get the following message:
"No filesystem could mount root, tried cramfs"
"Kernel
Still happening with this mornings update of the linux image.
--
will not boot 2.6.22-** linux image
https://bugs.launchpad.net/bugs/151132
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
I was not thinking but the 2.6.20-16 kernel was from my Feisty install.
So I would assume that I did have a working 2.6.22-** kernel working at
one time. I upgraded to Gutsy Beta on September 29, and the problem
started on 10/3.
--
will not boot 2.6.22-** linux image
https://bugs.launchpad.net/bu
Does "update-initramfs -k all -u" followed by a reboot make it boot
successfully into the 2.6.22 kernel? If so, this is a duplicate of
149565.
** Changed in: linux-source-2.6.22 (Ubuntu)
Sourcepackagename: None => linux-source-2.6.22
--
will not boot 2.6.22-** linux image
https://bugs.launchpad.
I just ran "update-initramfs -k all -u" and know no image will boot.
--
will not boot 2.6.22-** linux image
https://bugs.launchpad.net/bugs/151132
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
** Description changed:
- When I get right passed the bios screen before I get to the Ubuntu
- splash I get the following message:
+ When I get right pass the bios screen before I get to the Ubuntu splash
+ I get the following message:
"No filesystem could mount root, tried cramfs"
"Kernel
Still happening with this mornings update of the linux image.
--
will not boot 2.6.22-** linux image
https://bugs.launchpad.net/bugs/151132
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
I was not thinking but the 2.6.20-16 kernel was from my Feisty install.
So I would assume that I did have a working 2.6.22-** kernel working at
one time. I upgraded to Gutsy Beta on September 29, and the problem
started on 10/3.
--
will not boot 2.6.22-** linux image
https://bugs.launchpad.net/bu
** Description changed:
- When I get right passed the bios screen before I get to the Ubuntu
- splash I get the following message:
+ When I get right pass the bios screen before I get to the Ubuntu splash
+ I get the following message:
"No filesystem could mount root, tried cramfs"
"Kernel
Still happening with this mornings update of the linux image.
--
will not boot 2.6.22-** linux image
https://bugs.launchpad.net/bugs/151132
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
I was not thinking but the 2.6.20-16 kernel was from my Feisty install.
So I would assume that I did have a working 2.6.22-** kernel working at
one time. I upgraded to Gutsy Beta on September 29, and the problem
started on 10/3.
--
will not boot 2.6.22-** linux image
https://bugs.launchpad.net/bu
Does "update-initramfs -k all -u" followed by a reboot make it boot
successfully into the 2.6.22 kernel? If so, this is a duplicate of
149565.
** Changed in: linux-source-2.6.22 (Ubuntu)
Sourcepackagename: None => linux-source-2.6.22
--
will not boot 2.6.22-** linux image
https://bugs.launchpad.
I just ran "update-initramfs -k all -u" and know no image will boot.
--
will not boot 2.6.22-** linux image
https://bugs.launchpad.net/bugs/151132
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
** Description changed:
- When I get right passed the bios screen before I get to the Ubuntu
- splash I get the following message:
+ When I get right pass the bios screen before I get to the Ubuntu splash
+ I get the following message:
"No filesystem could mount root, tried cramfs"
"Kernel
Still happening with this mornings update of the linux image.
--
will not boot 2.6.22-** linux image
https://bugs.launchpad.net/bugs/151132
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
I was not thinking but the 2.6.20-16 kernel was from my Feisty install.
So I would assume that I did have a working 2.6.22-** kernel working at
one time. I upgraded to Gutsy Beta on September 29, and the problem
started on 10/3.
--
will not boot 2.6.22-** linux image
https://bugs.launchpad.net/bu
Does "update-initramfs -k all -u" followed by a reboot make it boot
successfully into the 2.6.22 kernel? If so, this is a duplicate of
149565.
** Changed in: linux-source-2.6.22 (Ubuntu)
Sourcepackagename: None => linux-source-2.6.22
--
will not boot 2.6.22-** linux image
https://bugs.launchpad.
I just ran "update-initramfs -k all -u" and know no image will boot.
--
will not boot 2.6.22-** linux image
https://bugs.launchpad.net/bugs/151132
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
Does "update-initramfs -k all -u" followed by a reboot make it boot
successfully into the 2.6.22 kernel? If so, this is a duplicate of
149565.
** Changed in: linux-source-2.6.22 (Ubuntu)
Sourcepackagename: None => linux-source-2.6.22
--
will not boot 2.6.22-** linux image
https://bugs.launchpad.
I just ran "update-initramfs -k all -u" and know no image will boot.
--
will not boot 2.6.22-** linux image
https://bugs.launchpad.net/bugs/151132
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
** Description changed:
- When I get right passed the bios screen before I get to the Ubuntu
- splash I get the following message:
+ When I get right pass the bios screen before I get to the Ubuntu splash
+ I get the following message:
"No filesystem could mount root, tried cramfs"
"Kernel
Still happening with this mornings update of the linux image.
--
will not boot 2.6.22-** linux image
https://bugs.launchpad.net/bugs/151132
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
I was not thinking but the 2.6.20-16 kernel was from my Feisty install.
So I would assume that I did have a working 2.6.22-** kernel working at
one time. I upgraded to Gutsy Beta on September 29, and the problem
started on 10/3.
--
will not boot 2.6.22-** linux image
https://bugs.launchpad.net/bu
Does "update-initramfs -k all -u" followed by a reboot make it boot
successfully into the 2.6.22 kernel? If so, this is a duplicate of
149565.
** Changed in: linux-source-2.6.22 (Ubuntu)
Sourcepackagename: None => linux-source-2.6.22
--
will not boot 2.6.22-** linux image
https://bugs.launchpad.
I just ran "update-initramfs -k all -u" and know no image will boot.
--
will not boot 2.6.22-** linux image
https://bugs.launchpad.net/bugs/151132
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
** Description changed:
- When I get right passed the bios screen before I get to the Ubuntu
- splash I get the following message:
+ When I get right pass the bios screen before I get to the Ubuntu splash
+ I get the following message:
"No filesystem could mount root, tried cramfs"
"Kernel
Still happening with this mornings update of the linux image.
--
will not boot 2.6.22-** linux image
https://bugs.launchpad.net/bugs/151132
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
I was not thinking but the 2.6.20-16 kernel was from my Feisty install.
So I would assume that I did have a working 2.6.22-** kernel working at
one time. I upgraded to Gutsy Beta on September 29, and the problem
started on 10/3.
--
will not boot 2.6.22-** linux image
https://bugs.launchpad.net/bu
30 matches
Mail list logo
