From: Kenji M. <ken...@gm...> - 2005-10-27 00:16:15
|
Hello, I've made a few attempts starting the colinux-daemon on the Gentoo filesystem downloaded in the installer., but with a few errors. C:\Program Files\coLinux>colinux-daemon -c colinux.default.xml Cooperative Linux Daemon, 0.6.2 Compiled on Sat Feb 5 10:19:28 2005 daemon: exit code 84a08401 daemon: error - CO_RC_ERROR_ERROR, line 33, file colinux/os/current/user/fi= le.o (37) The text below is copied from the colinux.default.config. <?xml version=3D"1.0" encoding=3D"UTF-8"?> <colinux> <!-- This line needs to point to your root file system. =09 For example change "root_fs" to the name of the Debian image. Inside coLinux it will be /dev/cobd0 =09 =09 Block Device Aliasing: You can now handle most dual-boot issues =09 by adding an alias=3D"devname" to block_device. i.e. alias=3D"hda", =09 alias=3D"hda1" You can do this for SCSI as well as IDE. You need =09 to be aware that if you add an alias, you need to change your =09 bootparams root=3D"devname" appropriately (you may need to use =09 devfs naming in some situations). --> <block_device index=3D"0" path=3D"\DosDevices\c:\Progam Files\coLinux\Gentoo-colinux-stage3-x86-2004.3" enabled=3D"true" /> <!-- This line can specify a swap file if you wish, or an additional image file, it will /dev/cobd1. Additional block_devices can =09 be specified in the same manner by increasing the index --> <block_device index=3D"1" path=3D"\DosDevices\c:\Progam Files\coLinux\swap_file" 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" /> <!-- image allows you to specify the kernel to boot --> <image path=3D"vmlinux" /> <!-- this line allows you to specify the amount of memory available to coLinux --> <memory size=3D"256" /> <!-- 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> What have I done incorrectly? - Neil |
From: Sam M. <pa...@gm...> - 2005-10-27 03:18:38
|
Off the top of my head that looks like there is an issue with one of your images. Double check your paths and also double checkt that you unzipped them first. Sam On 10/27/05, Kenji Miyamoto <ken...@gm...> wrote: > Hello, > > I've made a few attempts starting the colinux-daemon on the Gentoo > filesystem downloaded in the installer., but with a few errors. > > C:\Program Files\coLinux>colinux-daemon -c colinux.default.xml > Cooperative Linux Daemon, 0.6.2 > Compiled on Sat Feb 5 10:19:28 2005 > > daemon: exit code 84a08401 > daemon: error - CO_RC_ERROR_ERROR, line 33, file colinux/os/current/user/= file.o > (37) > > > The text below is copied from the colinux.default.config. > > > <?xml version=3D"1.0" encoding=3D"UTF-8"?> > <colinux> > <!-- This line needs to point to your root file system. > For example change "root_fs" to the name of the Debian image. > Inside coLinux it will be /dev/cobd0 > > Block Device Aliasing: You can now handle most dual-boot issues > by adding an alias=3D"devname" to block_device. i.e. alias=3D"hd= a", > alias=3D"hda1" You can do this for SCSI as well as IDE. You nee= d > 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:\Progam > Files\coLinux\Gentoo-colinux-stage3-x86-2004.3" > enabled=3D"true" /> > > <!-- 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:\Progam > Files\coLinux\swap_file" > 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" /> > > <!-- image allows you to specify the kernel to boot --> > <image path=3D"vmlinux" /> > > <!-- this line allows you to specify the amount of memory available > to coLinux --> > <memory size=3D"256" /> > > <!-- 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> > > What have I done incorrectly? > > - Neil > > > ------------------------------------------------------- > This SF.Net email is sponsored by the JBoss Inc. > Get Certified Today * Register for a JBoss Training Course > Free Certification Exam for All Training Attendees Through End of 2005 > Visit http://www.jboss.com/services/certification for more information > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
From: Kenji M. <ken...@gm...> - 2005-10-27 03:42:54
|
Hello, I must've messed up the path to the root filesystem. A console appears now, but now I get the following errors: C:\Program Files\coLinux>colinux-daemon -c default.colinux.xml Cooperative Linux Daemon, 0.6.2 Compiled on Sat Feb 5 10:19:28 2005 Linux version 2.6.10-co-0.6.2 (ka...@ca...) (gcc version 3.3.5 (= Debia n 1:3.3.5-8)) #5 Sat Feb 5 10:19:16 IST 2005 256MB LOWMEM available. initrd enabled: start: 0xcfea2000 size: 0x0015db27) On node 0 totalpages: 65536 DMA zone: 0 pages, LIFO batch:1 Normal zone: 65536 pages, LIFO batch:16 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: 2048 (order: 11, 32768 bytes) Using cooperative for high-res timesource Console: colour CoCON 80x25 Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) auto selecting TAP found TAP device named "Local Area Connection 2" opening TAP: "Local Area Connection 2" driver version 8.1 enabling TAP... Memory: 254592k/262144k available (1502k kernel code, 0k reserved, 548k dat= a, 10 4k init, 0k highmem) Calibrating delay loop... 756.94 BogoMIPS (lpj=3D3784704) Mount-cache hash table entries: 512 (order: 0, 4096 bytes) CPU: After generic identify, caps: afe9fbff 00000000 00000000 00000000 CPU: After vendor identify, caps: afe9fbff 00000000 00000000 00000000 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 1024K CPU: After all inits, caps: afe9fbff 00000000 00000000 00000040 CPU: Intel(R) Celeron(R) M processor 1.50GHz stepping 08 Enabling fast FPU 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 an in= itrd 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 2048 buckets, 16Kbytes TCP: Hash tables configured (established 16384 bind 32768) NET: Registered protocol family 1 NET: Registered protocol family 17 RAMDISK: Compressed image found at block 0 EXT2-fs warning: checktime reached, running e2fsck is recommended VFS: Mounted root (ext2 filesystem). VFS: Cannot open root device "cobd0" or unknown-block(117,0) Please append a correct "root=3D" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1= 17,0) Why does this still happen, even after performing an e2fsck in Cygwin? - Kenji On 10/26/05, Sam Moffatt <pa...@gm...> wrote: > Off the top of my head that looks like there is an issue with one of > your images. Double check your paths and also double checkt that you > unzipped them first. > > Sam > > On 10/27/05, Kenji Miyamoto <ken...@gm...> wrote: > > Hello, > > > > I've made a few attempts starting the colinux-daemon on the Gentoo > > filesystem downloaded in the installer., but with a few errors. > > > > C:\Program Files\coLinux>colinux-daemon -c colinux.default.xml > > Cooperative Linux Daemon, 0.6.2 > > Compiled on Sat Feb 5 10:19:28 2005 > > > > daemon: exit code 84a08401 > > daemon: error - CO_RC_ERROR_ERROR, line 33, file colinux/os/current/use= r/file.o > > (37) > > > > > > The text below is copied from the colinux.default.config. > > > > > > <?xml version=3D"1.0" encoding=3D"UTF-8"?> > > <colinux> > > <!-- This line needs to point to your root file system. > > For example change "root_fs" to the name of the Debian image. > > Inside coLinux it will be /dev/cobd0 > > > > Block Device Aliasing: You can now handle most dual-boot issue= s > > 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 n= eed > > 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:\Progam > > Files\coLinux\Gentoo-colinux-stage3-x86-2004.3" > > enabled=3D"true" /> > > > > <!-- This line can specify a swap file if you wish, or an additiona= l > > 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:\Progam > > Files\coLinux\swap_file" > > 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" /> > > > > <!-- image allows you to specify the kernel to boot --> > > <image path=3D"vmlinux" /> > > > > <!-- this line allows you to specify the amount of memory available > > to coLinux --> > > <memory size=3D"256" /> > > > > <!-- This allows you to modify networking parameters, see the READM= E > > or website or wiki for more information --> > > <network index=3D"0" type=3D"tap" /> > > </colinux> > > > > What have I done incorrectly? > > > > - Neil > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by the JBoss Inc. > > Get Certified Today * Register for a JBoss Training Course > > Free Certification Exam for All Training Attendees Through End of 2005 > > Visit http://www.jboss.com/services/certification for more information > > _______________________________________________ > > coLinux-users mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-users > > > |
From: Red C. <le...@ya...> - 2005-10-27 20:50:59
|
Hello everyonw: I have the same problem, I'm try with debian an fedora in the finals steps say "kernel panic" and I don't know why is this problem because I have the swap file. In the two cases colinux don't know where is cobd0. --- Kenji Miyamoto <ken...@gm...> write: > Hello, > > I must've messed up the path to the root filesystem. > A console > appears now, but now I get the following errors: > > > C:\Program Files\coLinux>colinux-daemon -c > default.colinux.xml > Cooperative Linux Daemon, 0.6.2 > Compiled on Sat Feb 5 10:19:28 2005 > > Linux version 2.6.10-co-0.6.2 > (ka...@ca...) (gcc version 3.3.5 (Debia > n 1:3.3.5-8)) #5 Sat Feb 5 10:19:16 IST 2005 > 256MB LOWMEM available. > initrd enabled: start: 0xcfea2000 size: 0x0015db27) > On node 0 totalpages: 65536 > DMA zone: 0 pages, LIFO batch:1 > Normal zone: 65536 pages, LIFO batch:16 > HighMem zone: 0 pages, LIFO batch:1 > Built 1 zonelists > Kernel command line: root=/dev/cobd0 > Initializing CPU#0 > Setting proxy interrupt vectors > PID hash table entries: 2048 (order: 11, 32768 > bytes) > Using cooperative for high-res timesource > Console: colour CoCON 80x25 > Dentry cache hash table entries: 65536 (order: 6, > 262144 bytes) > Inode-cache hash table entries: 32768 (order: 5, > 131072 bytes) > auto selecting TAP > found TAP device named "Local Area Connection 2" > opening TAP: "Local Area Connection 2" > driver version 8.1 > enabling TAP... > Memory: 254592k/262144k available (1502k kernel > code, 0k reserved, 548k data, 10 > 4k init, 0k highmem) > Calibrating delay loop... 756.94 BogoMIPS > (lpj=3784704) > Mount-cache hash table entries: 512 (order: 0, 4096 > bytes) > CPU: After generic identify, caps: afe9fbff 00000000 > 00000000 00000000 > CPU: After vendor identify, caps: afe9fbff 00000000 > 00000000 00000000 > CPU: L1 I cache: 32K, L1 D cache: 32K > CPU: L2 cache: 1024K > CPU: After all inits, caps: afe9fbff 00000000 > 00000000 00000040 > CPU: Intel(R) Celeron(R) M processor 1.50GHz > stepping 08 > Enabling fast FPU 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 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 2048 buckets, > 16Kbytes > TCP: Hash tables configured (established 16384 bind > 32768) > NET: Registered protocol family 1 > NET: Registered protocol family 17 > RAMDISK: Compressed image found at block 0 > EXT2-fs warning: checktime reached, running e2fsck > is recommended > VFS: Mounted root (ext2 filesystem). > 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) > > > Why does this still happen, even after performing an > e2fsck in Cygwin? > > - Kenji > > > On 10/26/05, Sam Moffatt <pa...@gm...> wrote: > > Off the top of my head that looks like there is an > issue with one of > > your images. Double check your paths and also > double checkt that you > > unzipped them first. > > > > Sam > > > > On 10/27/05, Kenji Miyamoto > <ken...@gm...> wrote: > > > Hello, > > > > > > I've made a few attempts starting the > colinux-daemon on the Gentoo > > > filesystem downloaded in the installer., but > with a few errors. > > > > > > C:\Program Files\coLinux>colinux-daemon -c > colinux.default.xml > > > Cooperative Linux Daemon, 0.6.2 > > > Compiled on Sat Feb 5 10:19:28 2005 > > > > > > daemon: exit code 84a08401 > > > daemon: error - CO_RC_ERROR_ERROR, line 33, file > colinux/os/current/user/file.o > > > (37) > > > > > > > > > The text below is copied from the > colinux.default.config. > > > > > > > > > <?xml version="1.0" encoding="UTF-8"?> > > > <colinux> > > > <!-- This line needs to point to your root > file system. > > > For example change "root_fs" to the > name of the Debian image. > > > Inside coLinux it will be /dev/cobd0 > > > > > > Block Device Aliasing: You can now > handle most dual-boot issues > > > by adding an alias="devname" to > block_device. i.e. alias="hda", > > > alias="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="devname" appropriately > (you may need to use > > > devfs naming in some situations). --> > > > <block_device index="0" > path="\DosDevices\c:\Progam > > > Files\coLinux\Gentoo-colinux-stage3-x86-2004.3" > > > enabled="true" /> > > > > > > <!-- 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="1" > path="\DosDevices\c:\Progam > > > Files\coLinux\swap_file" > > > enabled="true" /> > > > > > > <!-- bootparams allows you to pass kernel > boot parameters --> > > > <bootparams>root=/dev/cobd0</bootparams> > > > > > > <!-- Initial RamDISK (initrd) support --> > > > <initrd path="initrd.gz" /> > > > > > > <!-- image allows you to specify the kernel > to boot --> > > > <image path="vmlinux" /> > > > > > > <!-- this line allows you to specify the > amount of memory available > > > to coLinux --> > > > <memory size="256" /> > > > > > > <!-- This allows you to modify networking > parameters, see the README > > > or website or wiki for more information > --> > > > <network index="0" type="tap" /> > > > </colinux> > > > > > > What have I done incorrectly? > > > > > > - Neil > === message truncated === ___________________________________________________________ Do You Yahoo!? La mejor conexión a Internet y <b >2GB</b> extra a tu correo por $100 al mes. http://net.yahoo.com.mx |
From: Henry N. <Henry.Ne@Arcor.de> - 2005-10-27 21:21:46
|
Red Crow wrote: > I have the same problem, I'm try with debian an > fedora in the finals steps say "kernel panic" and I > don't know why is this problem because I have the swap > file. In the two cases colinux don't know where is > cobd0. [...] >>VFS: Mounted root (ext2 filesystem). >>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 error is mostly a typofix in filname to the root_fs. Or you have not extraxt the file? Write again the entry for your image file, or move the image file to a smaler path for sample c:\colinux, then you can better verify the path and filename ;-) Make a backup of you XML file and remove or comment out all non used entries. Or create a new file with mininal entries you need: <?xml version="1.0" encoding="UTF-8"?> <colinux> <block_device index="0" path="\DosDevices\C:\colinux\my.img" enabled="true" / --> <bootparams>root=/dev/cobd0</bootparams> <image path="vmlinux" /> <memory size="64" /> </colinux> After this will boot, you can add step by step all others (swap, network, ...) -- Henry Nestler |
From: Henry N. <Henry.Ne@Arcor.de> - 2005-10-27 21:02:01
|
Kenji Miyamoto wrote: > Hello, > > I must've messed up the path to the root filesystem. A console > appears now, but now I get the following errors: > > > C:\Program Files\coLinux>colinux-daemon -c default.colinux.xml > Cooperative Linux Daemon, 0.6.2 > Compiled on Sat Feb 5 10:19:28 2005 > > Linux version 2.6.10-co-0.6.2 (ka...@ca...) (gcc version 3.3.5 (Debia > n 1:3.3.5-8)) #5 Sat Feb 5 10:19:16 IST 2005 > 256MB LOWMEM available. > initrd enabled: start: 0xcfea2000 size: 0x0015db27) Disable the initrd. colinux also runs without it. > On node 0 totalpages: 65536 > DMA zone: 0 pages, LIFO batch:1 > Normal zone: 65536 pages, LIFO batch:16 > HighMem zone: 0 pages, LIFO batch:1 > Built 1 zonelists > Kernel command line: root=/dev/cobd0 > Initializing CPU#0 > Setting proxy interrupt vectors > PID hash table entries: 2048 (order: 11, 32768 bytes) > Using cooperative for high-res timesource > Console: colour CoCON 80x25 > Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) > Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) > auto selecting TAP > found TAP device named "Local Area Connection 2" > opening TAP: "Local Area Connection 2" > driver version 8.1 > enabling TAP... > Memory: 254592k/262144k available (1502k kernel code, 0k reserved, 548k data, 10 > 4k init, 0k highmem) > Calibrating delay loop... 756.94 BogoMIPS (lpj=3784704) > Mount-cache hash table entries: 512 (order: 0, 4096 bytes) > CPU: After generic identify, caps: afe9fbff 00000000 00000000 00000000 > CPU: After vendor identify, caps: afe9fbff 00000000 00000000 00000000 > CPU: L1 I cache: 32K, L1 D cache: 32K > CPU: L2 cache: 1024K > CPU: After all inits, caps: afe9fbff 00000000 00000000 00000040 > CPU: Intel(R) Celeron(R) M processor 1.50GHz stepping 08 > Enabling fast FPU 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 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 2048 buckets, 16Kbytes > TCP: Hash tables configured (established 16384 bind 32768) > NET: Registered protocol family 1 > NET: Registered protocol family 17 > RAMDISK: Compressed image found at block 0 Here runs a ramdisk again? > EXT2-fs warning: checktime reached, running e2fsck is recommended > VFS: Mounted root (ext2 filesystem). > 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) Try some other boot options: root=/dev/cobd0 root=/dev/cobd/0 root=/dev/cobd0 ro > Why does this still happen, even after performing an e2fsck in Cygwin? Are you shure, that the file system is ext2 and ok? Boot a other linux, for sample a Knoppix, mount your image file as loop device and view into your file system. Are you shure, that you have unzipped the image without errors (with bunzip2)? -- Henry Nestler |