From: Henry N. <Hen...@Ar...> - 2007-04-16 19:07:40
|
Bill C. Riemers wrote: > I was trying to use coLinux 0.6.4, but no matter what I try it won't > recognize the root file system. It seems like the problem is either the > initrd.gz file, or the kernel. I am not sure which. For example I > downloaded the Debian image and renamed it root_fs so I could use the You should have unzip the image with bunzip2.exe http://www.henrynestler.com/colinux/tools/bzip2-102-x86-win32.zip The file Debian-3.0r2.ext3-mit-backports.1gb.bz2 is the latest debian and should have a size of exactly 1GB after unpacking. For the first boot you can also boot without initrd. Remove initrd from the xml config (or comment it out). > default.colinux.xml file. (That way I am certain I am not making a > typo.) But this is what I get: > > $ ./colinux-daemon.exe -c default.colinux.xml Please start coLinux not from a CygWin. Use a simple command prompt. The image file, you have renamed to 'root_fs' should exist in the directory c:\coLinux\, if use the default.colinux.xml, check it with an simple 'dir c:\coLinux\root_fs' in the same command prompt, you later try to start coLinux with: cd c:\coLinux dir c:\coLinux\root_fs colinux-daemon.exe -c default.colinux.xml > Cooperative Linux Daemon, 0.6.4 > Compiled on Mon May 29 22:19:09 2006 > > mapping cobd0 to \DosDevices\c:\coLinux\root_fs > mapping cobd1 to \DosDevices\c:\coLinux\swap_device > [...] > VFS: Cannot open root device "cobd0" or unknown-block(117,0) > Please append a correct "root=" boot option > Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(117,0) This is mostly an typofix in your filename of root_fs, or you have not uncompressed it, or the image file is demarged or incomplete. If you use the windows explorer, be shure, that you see the file extension "*.bz2", it's default hidden. -- Henry |