I cannot test yet anymore due to lack of hardware matching the
environment I was in (basically a 64-bit laptop with two HDs built in
using the alternative CD to install RAID1). I have two machines of that
kind out at customers but I cannot take them back yet for testing.
Maybe somebody else with
This bug report was marked as Incomplete and has not had any updated
comments for quite some time. As a result this bug is being closed.
Please reopen if this is still an issue in the current Ubuntu release
http://www.ubuntu.com/getubuntu/download . Also, please be sure to
provide any requested
How to apply the newest kernel if I must do a clean installation of
lucid configuring the RAID on installation?
On Mon, May 17, 2010 at 17:19, Jeremy Foshee
jeremy.fos...@canonical.com wrote:
Hi Martin,
If you could also please test the latest upstream kernel available that would
be great.
I tried to install the latest kernel after the first reboot.
Then further did updates and a few reboots.
So far it seems to work - error did not occur any more so far.
The only thing is: With this kernel I do now have other - completely
different - problems *ggmpf*.
--
Martin Wildam
**
Tested with Kernel: linux-
image-2.6.34-020634rc7-generic_2.6.34-020634rc7_amd64
--
1.5608-78 Kernel Panic _not syncing VFS: Unable to mount root FS on unknown
wvrblock(0,0)
https://bugs.launchpad.net/bugs/578560
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hi Martin,
If you could also please test the latest upstream kernel available that would
be great. It will allow additional upstream developers to examine the issue.
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the
upstream kernel, please remove the
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/48241356/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/48241357/AplayDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/48241358/BootDmesg.txt
**
