From: Sunil <fu...@ya...> - 2005-12-22 18:29:17
|
I am trying to run colinux-0.6.2 on windows xp x64. The problem is that I get an error when trying to start the daemon: ------------- D:\coLinux>colinux-daemon.exe -c D:\coLinux\default.colinux.xml.dumbgentoo -t nt colinux: manager open: last error: The system cannot find the file specified. 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) -------------- Here is my config.xml: *********************** D:\coLinux>type default.colinux.xml.dumbgentoo <?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\L:\coLinux\Gentoo-colinux-stage3-x 86-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\L:\coLinux\swap_1024Mb" enabled="true" /> <block_device index="2" path="\Device\Harddisk1\Partition3" enabled="true" / > <!-- bootparams allows you to pass kernel boot parameters --> <bootparams>root=/dev/cobd0</bootparams> <!-- Initial RamDISK (initrd) support --> <initrd path="\DosDevices\D:\coLinux\initrd.gz" /> <!-- image allows you to specify the kernel to boot --> <image path="\DosDevices\D:\coLinux\vmlinux" /> <!-- this line allows you to specify the amount of memory available to coLinux --> <memory size="512" /> <!-- This allows you to modify networking parameters, see the README or website or wiki for more information --> <!-- network index="0" type="tap" name="CoLinux TAP" / --> </colinux> **************** Both D: and L: are on a native NVRAID 0 setup. Is that the reason why its not able to find some (which I don't know) files? Please help. Thanks, Sunil __________________________________ Yahoo! for Good - Make a difference this year. http://brand.yahoo.com/cybergivingweek2005/ |
From: Henry N. <Henry.Ne@Arcor.de> - 2005-12-30 22:56:36
|
Sunil wrote: > I am trying to run colinux-0.6.2 on windows xp x64. > The problem is that I get an error when trying to > start the daemon: > > ------------- > D:\coLinux>colinux-daemon.exe -c > D:\coLinux\default.colinux.xml.dumbgentoo -t nt > colinux: manager open: last error: The system cannot > find the file specified. First check, that the driver is installed: colinux-daemon.exe --status-driver If not, reinstall it: colinux-daemon.exe --remove-driver colinux-daemon.exe --install-driver > 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) One of the file in config or the config was not found. > Both D: and L: are on a native NVRAID 0 setup. Is that > the reason why its not able to find some (which I > don't know) files? Think no, coLinux can use all windows files, that you are mapped with a drive letter. Please double check with a DIR on Wondows-Command prompt, that you all filenames wrote correctly, for sample: dir "L:\coLinux\Gentoo-colinux-stage3-x86-2004.3" dir "L:\coLinux\swap_1024Mb" dir "D:\coLinux\initrd.gz" dir "D:\coLinux\vmlinux" Have you enough access right for that files? Try to copy some of they into other directory. Try to view the files with some tools (WinCommander). If that not helps, try next: Comment out all devices from drive L:, comment out the initrd. Then comlpete remove the path "\DosDevices\D:\coLinux\" from vmlinux. Say simply: <image path="vmlinux" /> Change the current directory to the daemons and start it, for sample: D: cd \coLinux colinux-daemon.exe -c default.colinux.xml.dumbgentoo Now should the kernel boot and stop with error for root fs. Then enable the vmlinux, also so simple without paths: <initrd path="initrd.gz" /> and start colinux. Then reenable all you config lines step by step to find the error. -- Henry Nestler |
From: Sunil <fu...@ya...> - 2005-12-31 00:03:55
|
Thanks Henry for the response. The driver was not installed and --install-driver part failed with: ------------- I:\coLinux>colinux-daemon.exe --install-driver colinux: manager open: last error: The system cannot find the file specified. Cooperative Linux Daemon, 0.6.2 Compiled on Sat Feb 5 10:19:28 2005 loading I:\coLinux\linux.sys cannot install (8643bc0c) I:\coLinux> ------------- So, the install failed. I think this is the crux of the problem. If I solve this, those errors may go away. (I:\ is a drive not on the RAID.) Does this look like the 64-bit problem? XP Pro x64 is probably not allowing to install this driver. Thanks, Sunil --- Henry Nestler <Henry.Ne@Arcor.de> wrote: > > > Sunil wrote: > > > I am trying to run colinux-0.6.2 on windows xp > x64. > > The problem is that I get an error when trying to > > start the daemon: > > > > ------------- > > D:\coLinux>colinux-daemon.exe -c > > D:\coLinux\default.colinux.xml.dumbgentoo -t nt > > colinux: manager open: last error: The system > cannot > > find the file specified. > > First check, that the driver is installed: > colinux-daemon.exe --status-driver > > If not, reinstall it: > colinux-daemon.exe --remove-driver > colinux-daemon.exe --install-driver > > > 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) > > One of the file in config or the config was not > found. > > > Both D: and L: are on a native NVRAID 0 setup. Is > that > > the reason why its not able to find some (which I > > don't know) files? > > Think no, coLinux can use all windows files, that > you are mapped with a > drive letter. > > Please double check with a DIR on Wondows-Command > prompt, that you all > filenames wrote correctly, for sample: > > dir "L:\coLinux\Gentoo-colinux-stage3-x86-2004.3" > dir "L:\coLinux\swap_1024Mb" > dir "D:\coLinux\initrd.gz" > dir "D:\coLinux\vmlinux" > > Have you enough access right for that files? Try to > copy some of they > into other directory. Try to view the files with > some tools (WinCommander). > > If that not helps, try next: > Comment out all devices from drive L:, comment out > the initrd. Then > comlpete remove the path "\DosDevices\D:\coLinux\" > from vmlinux. Say > simply: > <image path="vmlinux" /> > Change the current directory to the daemons and > start it, for sample: > D: > cd \coLinux > colinux-daemon.exe -c > default.colinux.xml.dumbgentoo > Now should the kernel boot and stop with error for > root fs. > > Then enable the vmlinux, also so simple without > paths: > <initrd path="initrd.gz" /> > and start colinux. > > Then reenable all you config lines step by step to > find the error. > > -- > Henry Nestler > > __________________________________________ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com |
From: Henry N. <Henry.Ne@Arcor.de> - 2005-12-31 00:23:43
|
Sunil wrote: > loading I:\coLinux\linux.sys > cannot install (8643bc0c) Yes, that is a problem. But I can not solve it from this version. > So, the install failed. I think this is the crux of > the problem. If I solve this, those errors may go > away. (I:\ is a drive not on the RAID.) I think, it's no problem with raid :) > Does this look like the 64-bit problem? XP Pro x64 is > probably not allowing to install this driver. I don't know. Have no such system for testing. But, please use one of my last builds. Simple unzip the daemons and try to install the driver. http://www.henrynestler.com/colinux/testing/devel-2.6.12-hn/20051230/bin/daemons-0.7.1-hn10.zip If not works, please give me the error number again. If works, download also the rest, or the complete installer and rewrite your config from XML to new config file type (more simply, than the old). -- Henry Nestler |
From: Sunil <fu...@ya...> - 2005-12-31 01:35:37
|
no luck with the latest tar. I just downloaded what you mentioned. Uninstalled and cleaned the original install. Then unzipped just the link you pointed to and I get this: ------------------- I:\colinux>colinux-daemon.exe --install-driver Cooperative Linux Daemon, 0.7.1-hn10 Compiled on Mon Dec 26 01:27:41 2005 loading I:\colinux\linux.sys cannot install (8083d40c) ------------------- The error code is different this time. Thanks, -Sunil --- Henry Nestler <Henry.Ne@Arcor.de> wrote: > > > Sunil wrote: > > > loading I:\coLinux\linux.sys > > cannot install (8643bc0c) > > Yes, that is a problem. But I can not solve it from > this version. > > > So, the install failed. I think this is the crux > of > > the problem. If I solve this, those errors may go > > away. (I:\ is a drive not on the RAID.) > > I think, it's no problem with raid :) > > > Does this look like the 64-bit problem? XP Pro x64 > is > > probably not allowing to install this driver. > > I don't know. Have no such system for testing. > > But, please use one of my last builds. Simple unzip > the daemons and try > to install the driver. > http://www.henrynestler.com/colinux/testing/devel-2.6.12-hn/20051230/bin/daemons-0.7.1-hn10.zip > > If not works, please give me the error number again. > > If works, download also the rest, or the complete > installer and rewrite > your config from XML to new config file type (more > simply, than the old). > > -- > Henry Nestler > > __________________________________________ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com |
From: Henry N. <Henry.Ne@Arcor.de> - 2005-12-31 02:09:27
|
Sunil wrote: > no luck with the latest tar. I just downloaded what > you mentioned. Uninstalled and cleaned the original > install. Then unzipped just the link you pointed to > and I get this: > ------------------- > I:\colinux>colinux-daemon.exe --install-driver > Cooperative Linux Daemon, 0.7.1-hn10 > Compiled on Mon Dec 26 01:27:41 2005 > > loading I:\colinux\linux.sys > cannot install (8083d40c) > ------------------- > > The error code is different this time. Yeh, thanks! But with this version we can trace back the line number in source now. C:\>colinux-debug-daemon.exe -e 8083d40c Translate error code 8083d40c error - CO_RC_ERROR_ERROR_STARTING_DRIVER, line 245, file src/colinux/os/winnt/user/daemon/driver.c (4) This is this line in source: http://lxr.xpto.ath.cx/source/src/colinux/os/winnt/user/daemon/driver.c#L239 Sorry, but I can not help you here. Please write down your platform parameters (CPU, Memory, OS) to the list and ask some others, if it runs anywhere. -- Henry Nestler |
From: Sunil <fu...@ya...> - 2005-12-31 02:24:59
|
Hi, My CPU is Athlon X2 3800+, 2gb memory and running windows xp pro x64. If anyone with similar setup has successfully installed/run colinux, can you please post how you went about it. Thanks, Sunil --- Henry Nestler <Henry.Ne@Arcor.de> wrote: > Sunil wrote: > > > no luck with the latest tar. I just downloaded > what > > you mentioned. Uninstalled and cleaned the > original > > install. Then unzipped just the link you pointed > to > > and I get this: > > ------------------- > > I:\colinux>colinux-daemon.exe --install-driver > > Cooperative Linux Daemon, 0.7.1-hn10 > > Compiled on Mon Dec 26 01:27:41 2005 > > > > loading I:\colinux\linux.sys > > cannot install (8083d40c) > > ------------------- > > > > The error code is different this time. > > Yeh, thanks! But with this version we can trace back > the line number in > source now. > > C:\>colinux-debug-daemon.exe -e 8083d40c > Translate error code 8083d40c > error - CO_RC_ERROR_ERROR_STARTING_DRIVER, line > 245, file > src/colinux/os/winnt/user/daemon/driver.c (4) > > This is this line in source: > http://lxr.xpto.ath.cx/source/src/colinux/os/winnt/user/daemon/driver.c#L239 > > Sorry, but I can not help you here. > > Please write down your platform parameters (CPU, > Memory, OS) to the list > and ask some others, if it runs anywhere. > > -- > Henry Nestler > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do > you grep through log files > for problems? Stop! Download the new AJAX search > engine that makes > searching your log files as easy as surfing the > web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > __________________________________ Yahoo! for Good - Make a difference this year. http://brand.yahoo.com/cybergivingweek2005/ |
From: David L. <dle...@di...> - 2005-12-31 02:30:32
|
What would be the config entry for assigning a CD-ROM device? I've attempted to enter something similar to what would be in the stable XML config file, to no effect. Dave Leffler |
From: Henry N. <Henry.Ne@Arcor.de> - 2005-12-31 02:53:55
|
David Leffler wrote: > What would be the config entry for assigning a CD-ROM device? > > I've attempted to enter something similar to what would be in the stable XML > config file, to no effect. This works for me as /dev/hdc inside linux: <!-- CDROM --> <block_device index="4" path="\Device\Cdrom0" alias="hdc" enabled="true" /> -- Henry Nestler |
From: Henry N. <Henry.Ne@Arcor.de> - 2005-12-31 02:59:07
|
Henry Nestler wrote: > David Leffler wrote: > >> What would be the config entry for assigning a CD-ROM device? >> >> I've attempted to enter something similar to what would be in the >> stable XML >> config file, to no effect. > > > This works for me as /dev/hdc inside linux: > <!-- CDROM --> > <block_device index="4" path="\Device\Cdrom0" alias="hdc" > enabled="true" /> > Oh, sorry, for devel? # CDROM cobd4=\Device\Cdrom0 hdc=:cobd4 or simple: # CDROM hdc=\Device\Cdrom0 Full doc about config file you can read here: http://lxr.xpto.ath.cx/source/RUNNING http://lxr.xpto.ath.cx/source/doc/colinux-daemon -- Henry Nestler |
From: George P B. <geo...@gm...> - 2005-12-31 22:20:06
|
Hmm... Does the XP Pro x64 require that drivers be 64-bit. If it does, then the problem is that coLinux's windows driver is 32-bit. On 12/30/05, Sunil <fu...@ya...> wrote: > My CPU is Athlon X2 3800+, 2gb memory and running > windows xp pro x64. If anyone with similar setup has > successfully installed/run colinux, can you please > post how you went about it. -- George |
From: Sunil <fu...@ya...> - 2005-12-31 22:39:13
|
I think that's what the return code 1275 from StartService means: "Driver has been stopped from loading." So, we need to build the 64-bit version of colinux's windows driver. Anybody know how can one do that? I have no compiler on my machine apart from cygwin/mingw build environment (which I haven't used much before...:-)). --- George P Boutwell <geo...@gm...> wrote: > Hmm... Does the XP Pro x64 require that drivers be > 64-bit. If it > does, then the problem is that coLinux's windows > driver is 32-bit. > > On 12/30/05, Sunil <fu...@ya...> wrote: > > My CPU is Athlon X2 3800+, 2gb memory and running > > windows xp pro x64. If anyone with similar setup > has > > successfully installed/run colinux, can you > please > > post how you went about it. > > -- > George > __________________________________ Yahoo! for Good - Make a difference this year. http://brand.yahoo.com/cybergivingweek2005/ |
From: George P B. <geo...@gm...> - 2005-12-31 23:17:52
|
Hmm... Well, for starters you probably want/need monotone (http://www.venge.net/monotone), then you'll need to grab the latest coLinux source using it. After that you'll need an gcc 64-bit compiler for Linux or Windows and the same major/minor version of an 64bit cross-compiler (ie a compiler that runs in Linux, but builds gcc compatible win64 executables, or a compiler that runs in Windows, and builds gcc compatible elf (64-bit) executables). The reason you need a cross-compiler is because coLinux is part host, part guest code and the guest code needs to be compiled and compatible with the host code. After that you'll probably need lots of patience as you debug and fix all the 32-bit -> 64-bit porting problems/issues that you run into. On 12/31/05, Sunil <fu...@ya...> wrote: > I think that's what the return code 1275 from > StartService means: "Driver has been stopped from > loading." > > So, we need to build the 64-bit version of colinux's > windows driver. Anybody know how can one do that? I > have no compiler on my machine apart from cygwin/mingw > build environment (which I haven't used much > before...:-)). > -- George |
From: Sunil <fu...@ya...> - 2006-01-01 01:14:25
|
so, I need a native 64-bit linux compiler and a 64-bit cross compiler for win64. Both gcc same version. right? I do have a amd64 gentoo install lying on this very system, so I can put that to some use here. Are there instructions on build process for linux and windows parts using a linux machine? > as you debug and > fix all the 32-bit -> 64-bit porting problems/issues should I expect too many of these? Good to know beforehand what I am getting into...:) Thanks, -Sunil --- George P Boutwell <geo...@gm...> wrote: > Hmm... > > Well, for starters you probably want/need monotone > (http://www.venge.net/monotone), then you'll need to > grab the latest > coLinux source using it. > After that you'll need an gcc 64-bit compiler for > Linux or Windows > and the same major/minor version of an 64bit > cross-compiler (ie a > compiler that runs in Linux, but builds gcc > compatible win64 > executables, or a compiler that runs in Windows, and > builds gcc > compatible elf (64-bit) executables). The reason > you need a > cross-compiler is because coLinux is part host, part > guest code and > the guest code needs to be compiled and compatible > with the host code. > > After that you'll probably need lots of patience > as you debug and > fix all the 32-bit -> 64-bit porting problems/issues > that you run > into. > > On 12/31/05, Sunil <fu...@ya...> wrote: > > I think that's what the return code 1275 from > > StartService means: "Driver has been stopped from > > loading." > > > > So, we need to build the 64-bit version of > colinux's > > windows driver. Anybody know how can one do that? > I > > have no compiler on my machine apart from > cygwin/mingw > > build environment (which I haven't used much > > before...:-)). > > > > -- > George > __________________________________________ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com |
From: George P B. <geo...@gm...> - 2006-01-02 01:53:22
|
On 12/31/05, Sunil <fu...@ya...> wrote: > so, I need a native 64-bit linux compiler and a 64-bit > cross compiler for win64. Both gcc same version. > right? Correct. You need the same version gcc 64-bit compiler for both Linux and Windows. You'd be using the linux 64-bit compiler for the linux kernel itself and the Windows 64-bit compiler for the Windows host driver and daemons. > I do have a amd64 gentoo install lying on this very > system, so I can put that to some use here. Might be worth trying to get the coLinux in Linux working in 64-bit Linux before going after the cross-compile environment. > Are there instructions on build process for linux and > windows parts using a linux machine? Yes, in the source code tree there is the doc/building document.=20 Also, in the source code tree there is pretty much an ./configure and make process, which includes the cross-compile for you. However, it's all currently set-up for i686, so it would need some hacking for x64. > > as you debug and > > fix all the 32-bit -> 64-bit porting problems/issues > > should I expect too many of these? Good to know > beforehand what I am getting into...:) > No idea. I would expect typical 32 -> 64-bit problems, in addition to those I would expect problems with memory portion of coLinux's kernel patch, as memory probably isn't handled the same with x86 as it is with coLinux's, but it is virtual memory for the most part and might not make a difference. -- George |