From: Jacques M. <jac...@ne...> - 2005-07-10 18:20:28
|
I still can't get coLinux running using the config file but I can start the console using: colinux-daemon mem=256 kernel=vmlinux hda1=root_debian =/dev/hda1 but not colinux-daemon mem=256 kernel=vmlinux hda1=root_gentoo =/dev/hda1 Anyone having any idea what's going on ? |
From: udo 'm. f. <udo...@gm...> - 2005-07-11 08:44:13
|
Hi Jacques, On 7/10/05, Jacques Maeder <jac...@ne...> wrote: > I still can't get coLinux running using the config file but I can start t= he > console using: >=20 > colinux-daemon mem=3D256 kernel=3Dvmlinux hda1=3Droot_debian =3D/dev/hda= 1 >=20 > but not >=20 > colinux-daemon mem=3D256 kernel=3Dvmlinux hda1=3Droot_gentoo =3D/dev/hda1 where does the file root_debian reside, and where is root_gentoo on your system (i'd specify always full pathnames, even if it is not necessary)? if both files are in the same directory, what's the condition that let's you think it does not start? cu, -udo |
From: Henry N. <Henry.Ne@Arcor.de> - 2005-07-11 09:13:50
|
udo 'mju' fleckenstein wrote: > Hi Jacques, > > > On 7/10/05, Jacques Maeder <jac...@ne...> wrote: > >>I still can't get coLinux running using the config file but I can start the >>console using: >> >> colinux-daemon mem=256 kernel=vmlinux hda1=root_debian =/dev/hda1 >> >>but not >> >>colinux-daemon mem=256 kernel=vmlinux hda1=root_gentoo =/dev/hda1 > > > where does the file root_debian reside, and where is root_gentoo on > your system (i'd specify always full pathnames, even if it is not > necessary)? > > if both files are in the same directory, what's the condition that > let's you think it does not start? Try correct typo for block device and alias on command line. First set an image for block device "cobd1", than set the alias "hda1": colinux-daemon mem=256 kernel=vmlinux cobd1=root_gentoo hda1=:cobd1 -- Henry Nestler |
From: Jacques M. <jac...@ne...> - 2005-07-11 19:23:36
|
Hi, I corrected the typo (the missing root=) and then colinux-daemon kernel=vmlinux cobd0=root_fs hda2=:cobd0 root=/dev/cobd0 starts coLinux, but colinux-daemon mem=256 kernel=vmlinux cobd1=root_gentoo hda1=:cobd1 does not ! All my files are in c:\coLinux direction under Windows XP and NTFS (could it be a problem ?) I still have 2 problems: 1. The /lib/modules/2.6.10-co-0.6.2/modules.dep: is not found, but the file modules.dep is present in C:\coLinux\lib\modules\2.6.10-co-0.6.2. I however get the this error message when unzipping the vmlinux-modules.tar.gz: ! C:\coLinux\vmlinux-modules.tar.gz: Cannot open \home\karrde\colinux\linux-stable (\home\karrde\colinux\linux-stable --> lib\modules\2.6.10-co-0.6.2\source) ! C:\coLinux\vmlinux-modules.tar.gz: Symbolic link points to missing file 2. If I try to use the default.colinux.xml (see below) using: C:\coLinux\colinux-daemon.exe -c default.colinux.xml -t nt I get the errror message: 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) THANK'S for your help --------------------------------------- <?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:\coLinux\root_getoo" 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:\coLinux\swap_device" 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="Connexion_coLinux" /> --> ------------------ My coLinux directory contain the following files: Le volume dans le lecteur C s'appelle Main Le num,ro de s,rie du volume est C8F9-1A2D R,pertoire de C:\coLinux 11.07.2005 21:13 <REP> . 11.07.2005 21:13 <REP> .. 05.02.2005 10:18 2'951 cofs.txt 05.02.2005 10:19 286'154 colinux-bridged-net-daemon.exe 05.02.2005 10:19 723'992 colinux-console-fltk.exe 05.02.2005 10:19 415'753 colinux-console-nt.exe 05.02.2005 10:19 369'245 colinux-daemon.exe 05.02.2005 10:18 4'122 colinux-daemon.txt 05.02.2005 10:19 284'030 colinux-net-daemon.exe 05.02.2005 10:19 347'119 colinux-slirp-net-daemon.exe 11.07.2005 21:12 1'580 default.colinux.xml 11.07.2005 21:13 0 dir.txt 05.02.2005 13:44 3'145'728 initrd 08.07.2005 20:52 <REP> lib 05.02.2005 10:20 135'001 linux.sys 11.07.2005 21:02 0 LOG.TXT 08.07.2005 20:27 <REP> netdriver 05.02.2005 10:18 13'812 news.txt 05.02.2005 10:18 9'197 README.txt 11.07.2005 20:56 1'688'207'360 root_debian 11.07.2005 21:03 2'147'483'648 root_gentoo 08.07.2005 21:02 536'870'912 swap_device 08.07.2005 20:27 60'389 Uninstall.exe 05.02.2005 10:19 2'877'492 vmlinux 05.02.2005 10:19 1'007'394 vmlinux-modules.tar.gz 21 fichier(s) 4'382'245'879 octets 5 R,p(s) 84'587'003'904 octets libres |
From: Henry N. <Henry.Ne@Arcor.de> - 2005-07-12 07:53:36
|
Jacques Maeder wrote: > colinux-daemon kernel=vmlinux cobd0=root_fs hda2=:cobd0 root=/dev/cobd0 > starts coLinux, but > > colinux-daemon mem=256 kernel=vmlinux cobd1=root_gentoo hda1=:cobd1 > does not ! What is the error message? I missing "root=/dev/cobd1" here. I not know the default root file system device for gentoo. If it is cobd0 (see in your XML), you should use this also for command line boot: "colinux-daemon kernel=vmlinux cobd0=root_gentoo root=/dev/cobd0" The alias hdaX only need, if in your /etc/fstab use hdaX (X=0,1,2...) > All my files are in c:\coLinux direction under Windows XP and NTFS (could > it be a problem ?) No Prpblem. That is normal and right. > I still have 2 problems: > 1. The /lib/modules/2.6.10-co-0.6.2/modules.dep: is not found, but the file > modules.dep is present in C:\coLinux\lib\modules\2.6.10-co-0.6.2. I however > get the this error message when unzipping the vmlinux-modules.tar.gz: The modules should untar in running linux, so the tar create the directory /lib/modules/2.6.10-co-0.6.2 with the file modules.dep and all other modules. If you linux running, go into root of filesystem and untar the modules as user root. cd / tar xfz vmlinux-modules.tar.gz But you not need this for first start, all filesystem drivers are compiled in kernel. The file initrd.gz do the same for you. It extract the modules into your running root file system. > 2. If I try to use the default.colinux.xml (see below) using: > C:\coLinux\colinux-daemon.exe -c default.colinux.xml -t nt > > I get the errror message: > > 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) This message says: Any filename in XML file can't open. > <block_device index="0" path="\DosDevices\c:\coLinux\root_getoo" > enabled="true" /> Think, this is the typofix: root_getoo = root_gentoo -- Henry Nestler |
From: Jacques M. <jac...@ne...> - 2005-07-12 09:18:24
|
For the first command line, root=/dev/cobd1 was indeed missing, now it works. I'm used to DOS, Windows and a bit of MAC but new to LInux, where could I find explanations abouts hda, cobd.., and this kind of stuff (my purpose is to test Linux before switching from Windows to Linux) Also I cannot untar > untar vmlinux-modules.tar.gz > cd / > tar xfz vmlinux-modules.tar.gz It cannot find the vmlinux-modules.tar.gz file ! The problem with starting with the config file is actually not due to the typo, I get the same error message after correcting it. Finally I thought that I could access the Windows files from within coLinux, how could I do that ? Jacques Maeder |
From: Jacques M. <jac...@ne...> - 2005-07-12 10:01:29
|
I found that the problem with the config file is with: <initrd path="initrd.gz" /> if I comment it then I can start coLinux, what the use of it? and what could be wrong ? Jacques Maeder |
From: Henry N. <Henry.Ne@Arcor.de> - 2005-07-12 10:21:58
|
Jacques Maeder wrote: > I found that the problem with the config file is with: > > <initrd path="initrd.gz" /> > > if I comment it then I can start coLinux, what the use of it? and what could > be wrong ? Ah! Very good! > 05.02.2005 13:44 3'145'728 initrd You should not unzip this file. Please let this comressed (GZIP format) and with filename "initrd.gz". -- Henry Nestler |