RE: [coLinux-users] Install question

[Hurt, P. <Pau...@ad...>]

Hello Ewan,

   Here it is.  Since it is complaining about the root_fs line, I am
assuming I missed in the install, but I can't figure out what.

<?xml version=3D"1.0" encoding=3D"UTF-8"?>
<colinux>
    <!-- This line needs to point to your root file system.=20
  	 For example change "root_fs" to the name of the Debian image.
         Inside coLinux it will be /dev/cobd0=20
	=20
	 Block Device Aliasing: You can now handle most dual-boot issues
	 by adding an alias=3D"devname" to block_device. i.e. alias=3D"hda",
	 alias=3D"hda1" You can do this for SCSI as well as IDE.  You need
	 to be aware that if you add an alias, you need to change your
	 bootparams root=3D"devname" appropriately (you may need to use
	 devfs naming in some situations).  -->
    <block_device index=3D"0" path=3D"\DosDevices\c:\coLinux\root_fs"=20
    enabled=3D"true" />
   =20
    <!-- This line can specify a swap file if you wish, or an additional
         image file, it will /dev/cobd1. Additional block_devices can
	 be specified in the same manner by increasing the index -->

    <block_device index=3D"1" =
path=3D"\DosDevices\c:\coLinux\swap_device"=20
    enabled=3D"true" />

    <!-- bootparams allows you to pass kernel boot parameters -->
    <bootparams>root=3D/dev/cobd0</bootparams>

    <!-- Initial RamDISK (initrd) support -->
    <initrd path=3D"initrd.gz" />
   =20
    <!-- image allows you to specify the kernel to boot -->
    <image path=3D"vmlinux" />

    <!-- this line allows you to specify the amount of memory available=20
         to coLinux -->
    <memory size=3D"64" />

    <!-- This allows you to modify networking parameters, see the README

         or website or wiki for more information -->
    <network index=3D"0" type=3D"tap" />
</colinux>
=20

-----Original Message-----
From: col...@li...
[mailto:col...@li...] On Behalf Of Ewan
Grantham
Sent: Thursday, October 20, 2005 9:52 AM
To: Hurt, Paul
Cc: col...@li...
Subject: Re: [coLinux-users] Install question

It would help to see what's in your default.config.xml file which I
assume is in the same directory.

On 10/20/05, Hurt, Paul <Pau...@ad...> wrote:
>
>
> Hi there,
>
>   I am trying to install coLinux on my xp system and when I type:
> C:\coLinux>colinux-daemon.exe -c default.colinux.xml
>   This is what I get:
>
> Cooperative Linux Daemon, 0.6.2
> Compiled on Sat Feb  5 10:19:28 2005
>
> auto selecting TAP
> found TAP device named "Local Area Connection 3"
> opening TAP: "Local Area Connection 3"
> tap device open: last error: The system cannot find the file
specified.
> error opening TAP device (86c48401)
> Linux version 2.6.10-co-0.6.2 (ka...@ca...) (gcc version=20
> 3.3.5 (Debia n 1:3.3.5-8)) #5 Sat Feb 5 10:19:16 IST 2005 64MB LOWMEM=20
> available.
> initrd enabled: start: 0xc3ea2000  size: 0x0015db27) On node 0=20
> totalpages: 16384
>   DMA zone: 0 pages, LIFO batch:1
>   Normal zone: 16384 pages, LIFO batch:4
>   HighMem zone: 0 pages, LIFO batch:1
> Built 1 zonelists
> Kernel command line: root=3D/dev/cobd0
> Initializing CPU#0
> Setting proxy interrupt vectors
> PID hash table entries: 512 (order: 9, 8192 bytes) Using cooperative=20
> for high-res timesource
> Console: colour CoCON 80x25
> Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)=20
> Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
> Memory: 59920k/65536k available (1502k kernel code, 0k reserved, 548k=20
> data, 104k  init, 0k highmem) Calibrating delay loop... 629.14=20
> BogoMIPS (lpj=3D3145728) Mount-cache hash table entries: 512 (order: =
0,=20
> 4096 bytes)
> CPU: After generic identify, caps: bfebfbff 00000000 00000000 00000000
> CPU: After vendor identify, caps:  bfebfbff 00000000 00000000 00000000

> monitor/mwait feature present.
> using mwait in idle threads.
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 1024K
> CPU: After all inits, caps:        bfebfbff 00000000 00000000 00000080
> CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz stepping 01 Enabling fast FPU=20
> save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Checking 'hlt' instruction... OK.
> checking if image is initramfs...it isn't (no cpio magic); looks like=20
> an initrd Freeing initrd memory: 1398k freed
> NET: Registered protocol family 16
> devfs: 2004-01-31 Richard Gooch (rg...@at...)
> devfs: boot_options: 0x0
> cofuse init 0.1 (API version 2.2)
> Initializing Cryptographic API
> serio: cokbd at irq 1
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered
> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> elevator: using anticipatory as default io scheduler
> cobd: loaded (max 32 devices)
> loop: loaded (max 8 devices)
> conet: loaded (max 16 devices)
> conet0: initialized
> mice: PS/2 mouse device common for all mice
> input: AT Translated Set 2 keyboard on cokbd
> NET: Registered protocol family 2
> IP: routing cache hash table of 512 buckets, 4Kbytes
> TCP: Hash tables configured (established 4096 bind 8192)
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> RAMDISK: Compressed image found at block 0 EXT2-fs warning: checktime=20
> reached, running e2fsck is recommended
> VFS: Mounted root (ext2 filesystem).
> VFS: Cannot open root device "cobd0" or unknown-block(117,0) Please=20
> append a correct "root=3D" boot option Kernel panic - not syncing: =
VFS:=20
> Unable to mount root fs on
> unknown-block(117,0)
>
> I can't figure out what I am doing wrong?  Can anyone  help?
>
> Thanks,
> Paul


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads,
discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
coLinux-users mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-users