It could be the same issue. My problem was caused by an incorrect
/etc/fstab file that I wanted to work both with regular dual boot and
colinux. This worked up until CoLinux 0.6.2 but not 0.6.3. Henry
helped me with this, and here's my summary of it as I mailed it to
the list (so it should be on SF).
Hope this helps.
Henry was kind enough to resolve the missing modules directory
problem off-line for me after I sent him my /etc/fstab file. The
problem was that:
1) CoLinux parses /etc/fstab to find the root file system.
It does not do any testing (AFAIK) regarding the correctness
of the file, and picks the first root file system mount it finds.
With earlier versions it may have been the last one - this
explains why I did not have this problem with 0.6.2 (unless
something else happened that made it work, I can't remember).
If coLinux doesn't parse the right line, unzipping the modules
archive will fail.
2) I used a /etc/fstab that makes my Linux distro work both
stand-alone (dual-boot) and with coLinux. This requires
that the root file system be mounted differently (/dev/cobd0
or /dev/sda2 in my case - external USB drive). I found that
you can simply define the mount twice, the boot will report
an error for one line or the other depending on how you boot
but will continue and work fine otherwise. So I didn't bother
fixing my /etc/fstab file.
The solution that Henry pointed out to me was to use an alias
in my XML file:
<block_device index="0" path="\Device\Harddisk1\Partition2"
enabled="true" alias="sda2" />
This worked fine after I also removed the /etc/cobd0 line from
The alias keyword is documented in README.txt but not
well enough for most users to understand what it does I think
so I'll try to document it on the Wiki (if I can).
I remember there were some other files that may need to be
changed in order for dual-boot and coLinux operation, namely
/etc/inittab (set the run level to 3 to keep coLinux from starting
X), and /etc/rc.d/rc3.d/S05kudzu (disable kudzu by removing
or renaming it for coLinux). I'm now using it with VNC without
messing with these files, sometimes I have to hit F4 twice to
skip kudzu. I'm only a half-baked Linux user so if anybody
has a more elegant way of dealing with this (shouldn't be too
hard) please let me know and I'll document it as well.
----- Original Message -----
From: "Robert Mitchell" <rob-mitchell@...>
Sent: Thursday, July 06, 2006 8:35 AM
Subject: [coLinux-users] Missing /lib/modules/2.6.11-co-0.6.3
> 1. Please report what configuration you're using to run coLinux.
> Try to include:
> o What coLinux release version or snapshot datestamp you're running
> o 0.6.3-linux-2.6.11
> o What Linux disk image (Debian, Gentoo, etc.) you downloaded and
> are using Debian-3.02.ext3-mit-backports.1gb.bz2
> o Any major changes you've made to the configuration of your disk image
> o None
> o The contents of your default.coLinux.xml XML file if you've made
> some changes to it
> <?xml version="1.0" encoding="UTF-8"?>
> <block_device index="0"
> enabled="true" />
> <block_device index="1" path="\DosDevices\c:\colinux\swap.fs"
> enabled="true" />
> <block_device index="2" path="\Device\CdRom0" enabled="true">
> <bootparams>ro root=/dev/cobd0</bootparams>
> <image path="vmlinux"></image>
> <memory size="256"></memory>
> <network index='0' name='Local Area Connection 2'
> o What Windows OS version and Service Pack level you're using
> o Windows XP SP2
> o Any other changes (different versions of DLL's, Windows patches,
> etc.) you made - None
> o Your coLinux/Windows networking configuration (is the TAP-Win32
> virtual adapter using Internet Connection Sharing, is it bridged,
> o Tap-Win32 Adapter V8 (coLinux)
> 2. Please explain the problem you're having as best you can.
> Under V6.3 of coLinux:~# /lib/module# I see 2.6.10-co-0.6.2
> 2.6.10-co-0.6.2-pre and
> 2.6.10-co-0.7.0 and no 2.6.11-co-0.6.3 directory. Under windows
> c:\colinux it shows
> Lib\modules\2.6.11-co-0.6.3 with files under it. I pulled the
> CoLinux-0.6.3.exe from
> http://sourceforge.net/project/showfiles.php?group_id=98788 to
> build A Debian package. Error message is FATAL: could not load
> /lib/modules/2.6.11-co-0.6.3 /modules.dep no such file or
> directory. coLinux doesn't see the directory but Windows XP SP2
> does? My network doesn't come up. I have Local Area Connection 2
> bridged to Local Area Connection which says Network cable
> unplugged. I gave it an IP address of 192,168.2.40 and the Gateway
> is 192.168.2.1 and the mask is 255.255.255.0. CoLinux can ping
> 192.168.2.40 and Windows can ping itself 192.168.2.4 but they can't
> see each other. I don't think that coLinux can find the files in
> the 2.6.11-co-0.6.3 directory since it doesn't appear to exist in
> coLinux. How can I fix the problem?
> I see that Henk had the same problem on 5/13/06 but I didn't see a
> solution to the problem.
> Does anyone have any ideas?
> Search for businesses by name, location, or phone number. -Lycos Yellow
Search for businesses by name, location, or phone number. -Lycos Yellow
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
coLinux-users mailing list