colinux-users — coLinux users mailing list

Re: [coLinux-users] Losing Internet connection

[Dave C. <dc...@do...>]

On 8/20/07, Henry Nestler <Hen...@ar...> wrote:
>
> Dave Coventry wrote:
> > Most of the time it works fine.
> >
> > Then, suddenly, I will go to use portage (I've got the gentoo
> > installation), and it will be unable to find the servers.
> >
> > lynx will also not be able to access the net.
> >
> > If I do as Sam Moffat suggests, which is delete my XP lan connection and
> > reboot XP, windows rebuilds my Lan connection and my colinux
> > installation can access the Internet again. Which seems to suggest that
> > the problem is from the windows side.
> >
> > It's not really a big deal, but it is a bit of a pain.
>
> Removing and adding TAP for SLiRP is a very big pain. Because SLiRP
> works as normal winsock application. A normal windows logout or Reboot
> should go with slirp again. But normalny a new start of coLinux should
> be enough.


Well, I find that it requires the drastic method that I described before it
will reconnect. Rebooting windows doesn't do it.


In error case: Can you access to the internet from other windows
> applications, for example IE o other browsers?


Yes,  windows applications are not affected.

If this case exist in the next time, then please do some protocols from
> this state (before changing TAP):
> - is the colinux-slirp-net-daemon.exe running? (check with taskman)
> - is the ethernet card online and have a gateway? Check with
> "ipconfig.exe /all" and compair with a working session before.


Will do.

An other question: Have you some specials on the networking installed:
> - ICS?


No. There is the LAN connection, a 1394 connection and a wireless adapter.

- Special dial software for DSL or modem?


No, I use a network connection with the ADSL modem as a DHCP server.

- Have your network card a dynamic address?


Yes. In South Africa the Monopoly Telkom Company charges tenfold for static
IP addresses. Therefore, they do not like their customers to have an IP
address for too long and will force a reallocation.

   Is your gateway and DNS changed from time to time?


Yes, I think so.

   (Other mode would be an permanently address from local router.)
> - Firewall with idle timeout (for example ZoneAlarm does)


No.

I ask, because I every day use slirp for internet and tap for putty, and
> have long times no problems. And I'm hopping between different DHCP
> environments with my laptop.
> --
> Henry
>
>
Dave Coventry

Re: [coLinux-users] Losing Internet connection

[Henry N. <Hen...@Ar...>]

Dave Coventry wrote:
>  >What coLinux version you are using?
> Cooperative Linux Daemon, 0.8.0
> Compiled on Wed Apr 25 22:19:16 2007

Ok. Is good. There no such problems known. I can give some hints, hope 
one of will help you.

Please check, that TAP dosn't have an gateway.
TAP and your real Ethernet card should have different networks 
(192.168.4.0 and 192.168.0.0 in my example).
Here you can see an example from XP, where coLinux is running:

C:\>ipconfig
Windows-IP-Konfiguration

Ethernetadapter TAP-Colinux:
         Verbindungsspezifisches DNS-Suffix:
         IP-Adresse. . . . . . . . . . . . : 192.168.4.71
         Subnetzmaske. . . . . . . . . . . : 255.255.255.0
         Standardgateway . . . . . . . . . :

Ethernetadapter LAN-Connection:
         Verbindungsspezifisches DNS-Suffix: terminal
         IP-Adresse. . . . . . . . . . . . : 192.168.0.71
         Subnetzmaske. . . . . . . . . . . : 255.255.255.0
         Standardgateway . . . . . . . . . : 192.168.0.4

In my case slirp use the default gateway (german: "Standardgateway") 
192.168.0.4 for all outgoings.

If SLiRP is not working, then try "tracert.exe www.google.com" on 
Windows. Does this work?

C:\>tracert www.google.com

traceroute to www.google.com (209.85.129.147), 30 hops max:
   1    <1 ms    <1 ms    <1 ms  nameserver.local [192.168.0.4]
   ...

In the example should see your current gateway as first router (my 
192.168.0.4).

If slirp not working, then it's working with ipaddresses instead the 
names? This can be a problem with DNS. For example inside coLinux try to 
get www.google.com page (adress seen on windows side from tracert):
   cd /tmp
   wget 209.85.129.147

An fixed "HWaddr" in the coLinux config is mutch better for DHCP 
clients. Configure this in the coLinux config as follow:
   eth0=slirp,00:11:22:33:44:55

An other problem is perhaps the losing packets from dhcp. You would see 
the difference from working and non working by "ifconfig eth0" inside 
colinux, and compair all numbers in the line "inet addr:10.0.2.15 
Bcast:10.0.2.255  Mask:255.255.255.0". If some are different, then setup 
slirp inside coLinux with static address
http://colinux.wikia.com/wiki/Network#SLiRP_with_Static_IP_Address

Be carefully to have netmask 255.255.255.0 and broadcast 10.0.2.255 for 
slirp. SLiRP use non standard netmask.

-- 
Henry

Re: [coLinux-users] Losing Internet connection

[Dave C. <dgc...@gm...>]

>What coLinux version you are using?
Cooperative Linux Daemon, 0.8.0
Compiled on Wed Apr 25 22:19:16 2007


On 8/20/07, Henry Nestler <Hen...@ar...> wrote:
>
> Dave Coventry wrote:
> > Sam,
> >
> > Did you ever find out why XP stops allowing the Slirp connection from
> > Colinux?
> >
> > I keep finding I cannot connect, although removing the XP Local
> > connection does seem to cure it for a while, it's a pain to have to keep
> > doing this. Also, it seems to increment the name of the local connection
> > ("Local Area Connection 16").
>
> SLiRP should no hang on the TAP device. Under some situations the SLiRP
> hangs on the TAP instaed the real Ethernet for outgoing connections. For
> example, if you have no real Ethernet connection and the TAP device is
> "connected" before the slirp daemon starts.
> The 0.6.4 has an 10 sec timeout to re-connect over the current XP
> connection. So, should help to unplug the network cable (or "disable" in
> the network overview), wait 10 seconds and connect the cable (or
> "enable" the Ethernet card). Slirp should than read the current
> connection again and use the right DNS. As workarrount, you can add an
> other DNS behind the 10.0.2.15 in your resolve.conf
> The problem of old code: Slirp use the first connection, that is
> connected. This can also be the TAP device, and this would bad here.
>
> This all should solved in current coLinux versions (0.7.1 and 0.8.0
> Snapshots). There coLinux don't cache the DNS and don't bind on one of
> the network cards directly.
>
> What coLinux version you are using?
>
> PS: Slirp can't ping to the world, you can only test it with "wget ...".
> Slirp have no IMCP protocol, read more here:
> http://lists.gnu.org/archive/html/qemu-devel/2004-09/msg00192.html
>
> --
> Henry
>
>

Re: [coLinux-users] Losing Internet connection

[Henry N. <Hen...@Ar...>]

Dave Coventry wrote:
> Sam,
> 
> Did you ever find out why XP stops allowing the Slirp connection from 
> Colinux?
> 
> I keep finding I cannot connect, although removing the XP Local 
> connection does seem to cure it for a while, it's a pain to have to keep 
> doing this. Also, it seems to increment the name of the local connection 
> ("Local Area Connection 16").

SLiRP should no hang on the TAP device. Under some situations the SLiRP 
hangs on the TAP instaed the real Ethernet for outgoing connections. For 
example, if you have no real Ethernet connection and the TAP device is 
"connected" before the slirp daemon starts.
The 0.6.4 has an 10 sec timeout to re-connect over the current XP 
connection. So, should help to unplug the network cable (or "disable" in 
the network overview), wait 10 seconds and connect the cable (or 
"enable" the Ethernet card). Slirp should than read the current 
connection again and use the right DNS. As workarrount, you can add an 
other DNS behind the 10.0.2.15 in your resolve.conf
The problem of old code: Slirp use the first connection, that is 
connected. This can also be the TAP device, and this would bad here.

This all should solved in current coLinux versions (0.7.1 and 0.8.0 
Snapshots). There coLinux don't cache the DNS and don't bind on one of 
the network cards directly.

What coLinux version you are using?

PS: Slirp can't ping to the world, you can only test it with "wget ...". 
Slirp have no IMCP protocol, read more here: 
http://lists.gnu.org/archive/html/qemu-devel/2004-09/msg00192.html

-- 
Henry

Re: [coLinux-users] Setting up XDMCP

[Holger K. <hol...@gm...>]

Dave Coventry schrieb:
> 2. I have been unable to get XDMCP working.
> 
> ! The following three resources set up display :0 as the console.
> DisplayManager._0.setup:        /usr/lib/X11/xdm/Xsetup_0
> DisplayManager._0.startup:      /usr/lib/X11/xdm/GiveConsole
> DisplayManager._0.reset:        /usr/lib/X11/xdm/TakeConsole

These entrys most likely cause this:

> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> (EE) Unable to locate/open config file
> (EE) Failed to load module "vesa" (module does not exist, 0)
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> which would indicate that colinux is trying to open the local display.

make them a comment


> //netstat -a -n -p -u |grep 177
> 
> gives the following result:
> udp        0      0 0.0.0.0:177             0.0.0.0:*                           5896/gdm
> 
> 
> Anyone got any suggestions?

If gdm is up and running (i prefer kdm, even to start gnome, has a nicer interface) how do you try to connect, and what error do you get (if any)?

[coLinux-users] Setting up XDMCP

[Dave C. <dc...@do...>]

Hi,

Some time ago I had my Laptop stolen with a working CoLinux installation 
with Gentpoo [sorry, typo! but somehow it's appropriate!].

I have installed again and it is largely to my satisfaction except for 2 
issues

1. Every now and again I lose my internet connection.
2. I have been unable to get XDMCP working.

This is my configuration
~~~~~~~~~~~/etc/X11/xdm/Xaccess ~~~~~~~~~~~~~~
*                                       #any host can get a login window
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


~~~~~~~~~~~/etc/X11/xdm/xdm-config~~~~~~~~~~~~~
DisplayManager.errorLogFile:    /var/log/xdm.log
DisplayManager.pidFile:         /var/run/xdm.pid
DisplayManager.keyFile:         /etc/X11/xdm/xdm-keys
DisplayManager.servers:         /etc/X11/xdm/Xservers
DisplayManager.accessFile:      /etc/X11/xdm/Xaccess
DisplayManager*resources:       /etc/X11/xdm/Xresources
DisplayManager.willing:         /usr/lib/X11/xdm/Xwilling
! All displays should use authorization, but we cannot be sure
! X terminals may not be configured that way, so they will require
! individual resource settings.
DisplayManager*authorize:       true
!
DisplayManager*chooser:         /usr/lib/X11/xdm/chooser
DisplayManager*startup:         /usr/lib/X11/xdm/Xstartup
DisplayManager*session:         /usr/lib/X11/xdm/Xsession
DisplayManager*reset:           /usr/lib/X11/xdm/Xreset
DisplayManager*authComplain:    true
! The following three resources set up display :0 as the console.
DisplayManager._0.setup:        /usr/lib/X11/xdm/Xsetup_0
DisplayManager._0.startup:      /usr/lib/X11/xdm/GiveConsole
DisplayManager._0.reset:        /usr/lib/X11/xdm/TakeConsole

DisplayManager*loginmoveInterval:       10

! SECURITY: do not listen for XDMCP or Chooser requests
! Comment out this line if you want to manage X terminals with xdm
! DisplayManager.requestPort:   0
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~~~~~~~~~~~/etc/X11/gdm/custom.conf~~~~~~~~~~~~
0=inactive

[daemon]

[security]
DisallowTCP=false

[xdmcp]
Enable=true

[gui]

[greeter]

[chooser]

[debug]

# Note that to disable servers defined in the GDM System Defaults
# configuration file (such as 0=Standard, you must put a line in this file
# that says 0=inactive, as described in the Configuration section of the GDM
# documentation.
#
[servers]
Enable=false
0=Standard

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The Xorg.0.log file in /var/log/ had the following (EE) elements
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
(EE) Unable to locate/open config file
(EE) Failed to load module "vesa" (module does not exist, 0)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
which would indicate that colinux is trying to open the local display.

running

//netstat -a -n -p -u |grep 177

gives the following result:
udp        0      0 0.0.0.0:177             0.0.0.0:*                           5896/gdm


Anyone got any suggestions?
//

[coLinux-users] Losing Internet connection

[Dave C. <dc...@do...>]

Sam,

Did you ever find out why XP stops allowing the Slirp connection from 
Colinux?

I keep finding I cannot connect, although removing the XP Local 
connection does seem to cure it for a while, it's a pain to have to keep 
doing this. Also, it seems to increment the name of the local connection 
("Local Area Connection 16").

Many thank,

Dave Coventry

[coLinux-users] CoLinux not booting (exit code 84814401)

[Larry C. <lc...@di...>]

Hello,

I did a search of the archives at sourceforge. Apparantly, search is not
working since searching for terms (such as debian or colinux) known to be in
the subject or body of messages returns 0 results.

My install of Colinux has been working very well for several weeks. Along
the way I increased the disk image to 4 GB and have installed several
packages using dselect.

Now I'm getting an error on startup. There does not seem to be a way to
trouble-shoot the problem since the problem is in the disk image and the
disk image will not load. Am I forced to start from scratch?

I hope someone has encountered this before and can help me fix this.

Here is the boot sequence:
E:\CoLinux>colinux-daemon.exe -c config.xml
Cooperative Linux Daemon, 0.6.4
Compiled on Mon May 29 22:19:09 2006

mapping cobd0 to \DosDevices\E:\CoLinux\d.4gb
mapping cobd1 to \DosDevices\E:\CoLinux\swapfile
error initializing
daemon: exit code 84814401
daemon: error - CO_RC_ERROR_ERROR, line 81, file
colinux/os/current/user/manager.o (36)


Here is my xml file (comments removed):
<?xml version="1.0" encoding="UTF-8"?>
<colinux>
    <block_device index="0" path="\DosDevices\E:\CoLinux\d.4gb"
enabled="true" />
    <block_device index="1" path="\DosDevices\E:\CoLinux\swapfile"
enabled="true" />
    <bootparams>root=/dev/cobd0</bootparams>
    <initrd path="initrd.gz" />
    <image path="vmlinux" />
    <memory size="96" />
    <network index="0" type="bridged" name="Physical"
mac="34:56:78:9A:BC:DE" />
</colinux>
--
Larry Crouch
lc...@di...

Re: [coLinux-users] It's been 2 years since an official release...

[Anshul <ans...@gm...>]

VGhhbmtzIGEgbG90IGZvciB5b3VyIHJlcGx5LiAgSSB0aGluayBJIHdpbGwgZ28gd2l0aCB0aGUg
ZGV2IHNuYXBzaG90LgoKUGVyaGFwcywgdGhlIGNvbGludXggZGV2cyBzaG91bGQgY29uc2lkZXIg
cmVsZWFzaW5nIHNvbWUgc25hcHNob3QgYXMgYQpuZXcgcmVsZWFzZT8gICBUaGUgbGFzdCBvZmZp
Y2lhbCByZWxlYXNlIGlzIG5vdyB3YXkgdG9vIG9sZC4KCkFuc2h1bAoKT24gOC8xLzA3LCBIZW5y
eSBOZXN0bGVyIDxIZW5yeS5OZUBhcmNvci5kZT4gd3JvdGU6Cj4gQW5zaHVsIHdyb3RlOgo+ID4g
V2hlbiBjYW4gd2UgZXhwZWN0IGEgbmV3IG9uZT8gIDpQICBTZXJpb3VzbHksIHNob3VsZCBJIHdh
aXQgZm9yIGEgbmV3Cj4gPiByZWxlYXNlLCBnbyBmb3Igc3ZuIHN0YWJsZSBvciB1c2UgMC42LjQ/
Cj4KPiBUaGUgMC42LjQgc2hvdWxkIG5vdCB1c2UgZm9yIG5ldyBpbnN0YWxsYXRpb25zLgo+Cj4g
PiBJIGFtIG9uIHdpbiB4cCAgYW5kIGFtIGFib3V0IHRvIGluc3RhbGwgc2xhY2t3YXJlIDEyIG9u
IG15IGhkZCB3aGljaCBJCj4gPiB3aWxsIGJlIHJ1bm5pbmcgdGhyb3VnaCBteSBjb2xpbnV4IGhh
bGYgdGhlIHRpbWUuCj4KPiBGb3IgdmVyeSBzdGFibGUgcnVubmluZywgdXNlIHRoZSBsYXN0ZXN0
IHN0YWJsZSBSZWxlYXNlIENhbmRpZGF0ZQo+IDE0LUp1bC0yMDA3LCBjdXJyZW50bHkgdW5kZXIg
aHR0cDovL3d3dy5jb2xpbnV4Lm9yZy9zbmFwc2hvdHMvLCBpdCdzCj4ga2VybmVsIDIuNi4xMgo+
IFRoaXMgaGF2ZSBubyBob3RscHVnIGFuZCBubyB1ZGV2LiBGb3Igc29tZSBkaXN0cm9zIGl0IGlz
IHRvIG9sZC4KPgo+IE5ld2VyIGtlcm5lbCAyLjYuMTcgd2l0aCB1ZGV2IHN1cHBvcnQgaXMgYWxz
byBnb29kIHdvcmtpbmcuIFNlZSBkZXZlbAo+IHNuYXBzaG90IG9uIHRoZSBzYW1lIHBsYWNlLgo+
Cj4gLS0KPiBIZW5yeQo+CgoKLS0gCkkgaGF2ZSBubyBzcGVjaWFsIHRhbGVudHMuIEkgYW0gb25s
eSBwYXNzaW9uYXRlbHkgY3VyaW91cy4KICAgLS1BbGJlcnQgRWluc3RlaW4KLS0KaHR0cDovL3d3
dy5jbWkuYWMuaW4vfmFuc2h1bC8KaHR0cDovL2JhYm9vbmxvZ2ljLmNvbQotLQrgpIXgpILgpLbg
pYHgpLIgIOCkluCkguCkoeClh+CksuCkteCkvuCksgo=

Re: [coLinux-users] It's been 2 years since an official release...

[Henry N. <Hen...@Ar...>]

Anshul wrote:
> When can we expect a new one?  :P  Seriously, should I wait for a new
> release, go for svn stable or use 0.6.4?

The 0.6.4 should not use for new installations.

> I am on win xp  and am about to install slackware 12 on my hdd which I
> will be running through my colinux half the time.

For very stable running, use the lastest stable Release Candidate 
14-Jul-2007, currently under http://www.colinux.org/snapshots/, it's 
kernel 2.6.12
This have no hotlpug and no udev. For some distros it is to old.

Newer kernel 2.6.17 with udev support is also good working. See devel 
snapshot on the same place.

-- 
Henry

Re: [coLinux-users] Debian Etch from scratch initrd mount problem

[FaiF <fa...@gm...>]

Sorry for resending this email, I should use my subscribed email.

Hi All,

I have fixed this problem, Debian etch use new style initrds which is
in CPIO archive type. Currently colinux doesn't support it. I create a
16Mb image in ext2 format and copied Debian etch initrd files into
ext2 image. Then I can boot colinux using that image without any
problems and I can carry on installation from scratch. I uploaded this
ext2 image converted from Debian etch CPIO type initrd) to this link
so if anybody is interested in install debian from scratch you can use
mine: I will add this to wiki later.

http://wyonghao.googlepages.com/initrd-yw.gz

Cheers

Leo

On 27/07/07, FaiF <fa...@gm...> wrote:
> Hi All,
>
> I am new to colinux, at first I use current stable version 0.6.4, try
> to install debian etch from scratch as described from wiki:
> http://colinux.wikia.com/wiki/InstallDebianFromIso
>
> However, the error message is following:
> "...
> ReiserFS: cobd3: warning: sh-2021: reiserfs_fill_super: can not find
> reiserfs on cobd3
> VFS: Can't find ext3 filesystem on dev cobd3.
> VFS: Can't find an ext2 filesystem on dev cobd3.
> ..."
>
> I searched mailing lists and find some guy had same problem and the
> new wiki entry
> http://colinux.wikia.com/wiki/InstallDebianEtchFromIso
> suggests to use 0.7.1 and 0.8.0. I tried download 0.8.0 from:
> http://www.colinux.org/snapshots/
> And now still have errors like:
> "...
> No filesystem could mount root, tried:  reiserfs ext3 ext2 iso9660
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(117,3)
> ..."
>
> The initrd file I used is uncompressed from debian business card iso
> \install.386\initrd.gz using 7-zip. To ensure my config file is
> correct, I tested with Debian-4.0r0-etch.ext3.1gb.bz2 (uncompressed
> with 7-zip as well) from sf.net which boot colinux without any
> problems. I did install debian sarge from scratch one year ago without
> problem. Any one has any suggestions will be appreciated!
>
> Leo
>

Re: [coLinux-users] Debian Etch from scratch initrd mount problem (FIXED)

[Yonghao W. <wyo...@gm...>]

Hi All,

I have fixed this problem, Debian etch use new style initrds which is
in CPIO archive type. Currently colinux doesn't support it. I create a
16Mb image in ext2 format and copied Debian etch initrd files into
ext2 image. Then I can boot colinux using that image without any
problems and I can carry on installation from scratch. I uploaded this
ext2 image converted from Debian etch CPIO type initrd) to this link
so if anybody is interested in install debian from scratch you can use
mine:

http://wyonghao.googlepages.com/initrd-yw.gz

Cheers

Leo

On 27/07/07, FaiF <fa...@gm...> wrote:
> Hi All,
>
> I am new to colinux, at first I use current stable version 0.6.4, try
> to install debian etch from scratch as described from wiki:
> http://colinux.wikia.com/wiki/InstallDebianFromIso
>
> However, the error message is following:
> "...
> ReiserFS: cobd3: warning: sh-2021: reiserfs_fill_super: can not find
> reiserfs on cobd3
> VFS: Can't find ext3 filesystem on dev cobd3.
> VFS: Can't find an ext2 filesystem on dev cobd3.
> ..."
>
> I searched mailing lists and find some guy had same problem and the
> new wiki entry
> http://colinux.wikia.com/wiki/InstallDebianEtchFromIso
> suggests to use 0.7.1 and 0.8.0. I tried download 0.8.0 from:
> http://www.colinux.org/snapshots/
> And now still have errors like:
> "...
> No filesystem could mount root, tried:  reiserfs ext3 ext2 iso9660
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(117,3)
> ..."
>
> The initrd file I used is uncompressed from debian business card iso
> \install.386\initrd.gz using 7-zip. To ensure my config file is
> correct, I tested with Debian-4.0r0-etch.ext3.1gb.bz2 (uncompressed
> with 7-zip as well) from sf.net which boot colinux without any
> problems. I did install debian sarge from scratch one year ago without
> problem. Any one has any suggestions will be appreciated!
>
> Leo
>

[coLinux-users] Debian Etch from scratch initrd mount problem

[FaiF <fa...@gm...>]

Hi All,

I am new to colinux, at first I use current stable version 0.6.4, try
to install debian etch from scratch as described from wiki:
http://colinux.wikia.com/wiki/InstallDebianFromIso

However, the error message is following:
"...
ReiserFS: cobd3: warning: sh-2021: reiserfs_fill_super: can not find
reiserfs on cobd3
VFS: Can't find ext3 filesystem on dev cobd3.
VFS: Can't find an ext2 filesystem on dev cobd3.
..."

I searched mailing lists and find some guy had same problem and the
new wiki entry
http://colinux.wikia.com/wiki/InstallDebianEtchFromIso
suggests to use 0.7.1 and 0.8.0. I tried download 0.8.0 from:
http://www.colinux.org/snapshots/
And now still have errors like:
"...
No filesystem could mount root, tried:  reiserfs ext3 ext2 iso9660
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(117,3)
..."

The initrd file I used is uncompressed from debian business card iso
\install.386\initrd.gz using 7-zip. To ensure my config file is
correct, I tested with Debian-4.0r0-etch.ext3.1gb.bz2 (uncompressed
with 7-zip as well) from sf.net which boot colinux without any
problems. I did install debian sarge from scratch one year ago without
problem. Any one has any suggestions will be appreciated!

Leo

[coLinux-users] It's been 2 years since an official release...

[Anshul <ans...@gm...>]

When can we expect a new one?  :P  Seriously, should I wait for a new
release, go for svn stable or use 0.6.4?

I am on win xp  and am about to install slackware 12 on my hdd which I
will be running through my colinux half the time.

Thanks!

Anshul

Re: [coLinux-users] Are there any better/worse laptops for colinux

[Eric S. J. <es...@ha...>]

james pruett wrote:
> Hi,
> 
> Are there any better/worse laptops for colinux?
> Sorry to post this here, but laptops are expensive.
> HP,Vista,Dell, issues?

I have a negative recommendation for Acer.  I have a TravelMate 8200 and while 
the hardware and display are really nice, they have two huge negatives which 
means I'll never purchase one again.  The smaller of the two is the amount of 
heat it generates.  It's on the right-hand side and it's quite toasty when 
running a Linux virtual machine or speech recognition.  The biggest negative, 
however, is that the technical support cannot fog a mirror on a good day.  I 
have had persistent problems with Bluetooth which they cannot resolve.  Smaller 
negatives include never updating device drivers [1], being told (at $2.72 per 
minute) to scrub my disk, reinstall Windows and then after installing each 
application, try to cause the Bluetooth failure.  Note, I use a lot of 
applications so this suggestion would cost me at least a couple of weeks of down 
time.  And then the person says, "oh, that wouldn't do you any good because if 
an application makes Bluetooth go bad, it would only do it again."  even though 
I told them that the problem is an intermittent one and I could not afford the 
downtime,, they still kept trying to figure out how to make the reinstall 
process work.

Nice hardware, abysmal, worse than Dell support.  The only way I would purchase 
an Acer machine is if I was going to scrub the disk and install Linux from the 
first moment I popped it out of the box.

[1] what I mean by never updating drivers is that they never fix any bugs and 
then publish the fixes for your laptop.



-- 
Speech-recognition in use.  It makes mistakes, I correct some.

[coLinux-users] Are there any better/worse laptops for colinux

[james p. <gps...@gm...>]

Hi,

Are there any better/worse laptops for colinux?
Sorry to post this here, but laptops are expensive.
HP,Vista,Dell, issues?

Thanks for any leads.
jim pruett
http://www.gpscruise.com


-- 
privacy is about hiding a right, not a wrong.

[coLinux-users] Fwd: init runlevel 2 respawning too fast

[ray r. <ra...@go...>]

Hi,

I tried the easiest option and that hint did nicely the lastest snapshot
0.8.0 version with udev boots up fine without any issues. Thank you as awell
for the detail of the process.

On 6/25/07, Henry Nestler <Hen...@ar...> wrote:
>
> Hello Ray,
>
> ray ray wrote:
> > I am trying to install the crux linux distribution to use with
> > colinux. I am at the stage were the system should be booting up and
> > presenting the login prompt. The boot process goes upto the INIT
> > section and encounters a problem.
> >
> > ...
> > INIT: version 2.86 booting
> > The system is coming up.  Please wait.
> > /sbin/start_udev: line 7: /proc/sys/kernel/hotplug: No such file or
> directory
> > udevd[20]: main: the kernel does not support inotify, udevd can't
> monitor config
>
> ... Watch that line, udev is not working! You have no devices in /dev/
>
> > uration file changes
> > input: AT Translated Set 2 keyboard on cokbd
> > INIT: Entering runlevel: 2
> > INIT: Id "c1" respawning too fast: disabled for 5 minutes
> > INIT: Id "c2" respawning too fast: disabled for 5 minutes
> > INIT: Id "c3" respawning too fast: disabled for 5 minutes
> > INIT: Id "c4" respawning too fast: disabled for 5 minutes
> > INIT: Id "c5" respawning too fast: disabled for 5 minutes
> > INIT: Id "c6" respawning too fast: disabled for 5 minutes
>
> Your getty has no output device.
> This is typicaly a problem in distros with udev or other runtime created
> /dev/ directories.
>
> Mount your root filesystem from an other Live Linux and create some very
> importend devices:
>    /dev/tty0, /dev/tty1, ... /dev/tty6, /dev/null, /dev/zero
> The device node you will find with an "ls -la /dev/tty?" from your live
> system.
> Then the init should run.
> Next step is to create also your used root partions, for example:
>    /dev/hda1 or /dev/cobd0 (or /dev/cobd/0 in some cases)
>
> There is no problem, if any other process would later remount this with
> an udev. But you need this devices for your boot for non working udev.
>
> Hint: The latest snapshort of coLinux version 0.8.0 has a working udev
> (hotplug) support.
>

[coLinux-users] resuming from hibernate causes BSOD

[James H. <Jam...@ro...>]

I have experienced a major difficulty with coLinux, using version 0.6.4.
When I hibernate Windows XP with coLinux running, upon resume I almost always 
get the "blue screen of death". Is this a known issue? Could low hard disk 
space be the cause?

Using "Stand By" instead of hibernate is not so good, especially since the 
computer seems to turn on periodically when in standby mode. 

Cheers,
James

Re: [coLinux-users] Problems with cofs and .c Files : error: stray '\240'

[Henry N. <Hen...@Ar...>]

Hello Tiago,

Henry Nestler schrieb:
> Tiago Jost wrote:
>> ...
>> If I just mount the Windows partition, and try to compile the project 
>> inside the mount point (like /mnt/win/c/Project), I got errors, on some 
>> files, like:
>> crypt.*c*:1350: *error*: *stray* '\240' in program
>>
>> But the c file have just 1350 lines , for example, and the errors continue
> 
> The gcc internalny use 'mmap' to map your file into memory instead to 
> read the file directly. Some times gcc reads behind the end of file, so 
> you gets errors behid your last line of source file.

have fixed now, please use build from snapshot 20070708 build:
http://www.colinux.org/snapshots  or
http://www.henrynestler.com/colinux/testing/devel-0.8.0/20070708-Snapshot/packages/

--
Henry

Re: [coLinux-users] Internet stopped working

[Dave C. <dc...@do...>]

Robert Irvin wrote:
> Have you set up /etc/resolv.conf to specify your nameservers?
/etc/resolv.conf has:
nameserver 10.0.2.3

Which is presumably handled by the Colinux slirp implementation.....

Dave Coventry wrote:
> Well that's me flummoxed!
>
> I started up using the original rootfile and it worked!
>
> Sorry to have wasted everyone's time on this....
>
> Sam Moffatt wrote:
>> Yes, thats something to do on the Windows side. Its strange but it has
>> been a solution in the past for magically not working internet on
>> other devices. Remember everything still goes through windows so if it
>> has managed to corrupt itself (or just your tap interface) it might be
>> enough to destroy your colinux connectivity.
>>
>> On the colinux side, if both your routes look sane and your ifconfig
>> looks sane to me I would suggest that things should be working fine.
>> You could change connectivity method but it looks like its working
>> well.
>>
>> Debugging this stuff is always...fun :p
>>
>> Sam
>>
>> On 08/07/07, Dave Coventry <dc...@do...> wrote:
>>> Hi Sam, thanks for the response.
>>>
>>> Do you mean on the Windows side?
>>>
>>> I've just built a clean gentoo-root file and the interenet connection
>>> works fine, so it must be some change I've made to the colinux system.
>>>
>>> I might fiddle around with some of the files in /etc/conf.d/......
>>>
>>> Can you suggest some configuration files to look at?
>>>
>>> Sam Moffatt wrote:
>>> > This is rather silly but it has worked in the past. Delete all of 
>>> your
>>> > network devices, reboot and reinstall everything (namely the tap
>>> > devices, the rest should autodetect) and see if this fixes things.
>>> > I've seen it work once in the past with XP on this list and I've used
>>> > it a few times under earlier operating systems (especially 98). This
>>> > is only relevant if its been working and randomly seems to have
>>> > stopped working which I think is your case,
>>> >
>>> > Sam
>>> >
>>> > On 07/07/07, Dave Coventry <dc...@do...> wrote:
>>> >> Hi,
>>> >>
>>> >> I'm using the Genntoo build on Windows XP.
>>> >>
>>> >> I had everything running perfectly with eth0=slirp and eth1=tuntp.
>>> >>
>>> >> /etc/conf.d/net had:
>>> >> config_eth0=( "dchp" )
>>> >> config_eth1=( "192.168.37.20/24" )
>>> >>
>>> >> I could ssh to the colinux layer via eth1 and use portage 
>>> successfully
>>> >> on eth0.
>>> >>
>>> >> Now portage has stopped working and I cannot ping google or access
>>> >> www.yahoo.com with lynx. The Tuntap connection to the XP layer 
>>> remains
>>> >> intact.
>>> >>
>>> >> I'm not sure what I might have done to disrupt the eth0 service. 
>>> I have
>>> >> installed apache, but turning apache off does not help.
>>> >>
>>> >> Can anyone think of anything I can check?
>>> >>
>>> >> ifconfig tells me:
>>> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> >>
>>> >> eth0      Link encap:Ethernet  HWaddr 00:FF:E8:32:BD:00
>>> >>           inet addr:10.0.2.15  Bcast:10.0.2.255  Mask:255.255.255.0
>>> >>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>> >>           RX packets:25 errors:0 dropped:0 overruns:0 frame:0
>>> >>           TX packets:189 errors:0 dropped:0 overruns:0 carrier:0
>>> >>           collisions:0 txqueuelen:1000
>>> >>           RX bytes:1050 (1.0 Kb)  TX bytes:14282 (13.9 Kb)
>>> >>           Interrupt:2
>>> >>
>>> >> eth1      Link encap:Ethernet  HWaddr 00:FF:F9:56:80:00
>>> >>           inet addr:192.168.37.20  Bcast:192.168.37.255
>>> >> Mask:255.255.255.0
>>> >>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>> >>           RX packets:372 errors:0 dropped:0 overruns:0 frame:0
>>> >>           TX packets:498 errors:0 dropped:0 overruns:0 carrier:0
>>> >>           collisions:0 txqueuelen:1000
>>> >>           RX bytes:29783 (29.0 Kb)  TX bytes:69384 (67.7 Kb)
>>> >>           Interrupt:2
>>> >>
>>> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> >>
>>> >> (I had my old laptop stolen in a burglary and I'm trying to set 
>>> up the
>>> >> replacement)
>>> >>
>>> >> 
>>> ------------------------------------------------------------------------- 
>>>
>>> >>
>>> >> This SF.net email is sponsored by DB2 Express
>>> >> Download DB2 Express C - the FREE version of DB2 express and take
>>> >> control of your XML. No limits. Just data. Click to get it now.
>>> >> http://sourceforge.net/powerbar/db2/
>>> >> _______________________________________________
>>> >> coLinux-users mailing list
>>> >> coL...@li...
>>> >> https://lists.sourceforge.net/lists/listinfo/colinux-users
>>> >>
>>> >
>>> >
>>>
>>>
>>
>>
>
>

Re: [coLinux-users] Internet stopped working

[Sam M. <pa...@gm...>]

This is rather silly but it has worked in the past. Delete all of your
network devices, reboot and reinstall everything (namely the tap
devices, the rest should autodetect) and see if this fixes things.
I've seen it work once in the past with XP on this list and I've used
it a few times under earlier operating systems (especially 98). This
is only relevant if its been working and randomly seems to have
stopped working which I think is your case,

Sam

On 07/07/07, Dave Coventry <dc...@do...> wrote:
> Hi,
>
> I'm using the Genntoo build on Windows XP.
>
> I had everything running perfectly with eth0=slirp and eth1=tuntp.
>
> /etc/conf.d/net had:
> config_eth0=( "dchp" )
> config_eth1=( "192.168.37.20/24" )
>
> I could ssh to the colinux layer via eth1 and use portage successfully
> on eth0.
>
> Now portage has stopped working and I cannot ping google or access
> www.yahoo.com with lynx. The Tuntap connection to the XP layer remains
> intact.
>
> I'm not sure what I might have done to disrupt the eth0 service. I have
> installed apache, but turning apache off does not help.
>
> Can anyone think of anything I can check?
>
> ifconfig tells me:
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> eth0      Link encap:Ethernet  HWaddr 00:FF:E8:32:BD:00
>           inet addr:10.0.2.15  Bcast:10.0.2.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:25 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:189 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:1050 (1.0 Kb)  TX bytes:14282 (13.9 Kb)
>           Interrupt:2
>
> eth1      Link encap:Ethernet  HWaddr 00:FF:F9:56:80:00
>           inet addr:192.168.37.20  Bcast:192.168.37.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:372 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:498 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:29783 (29.0 Kb)  TX bytes:69384 (67.7 Kb)
>           Interrupt:2
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> (I had my old laptop stolen in a burglary and I'm trying to set up the
> replacement)
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>


-- 
Sam Moffatt
http://pasamio.id.au

[coLinux-users] Internet stopped working

[Dave C. <dc...@do...>]

Hi,

I'm using the Genntoo build on Windows XP.

I had everything running perfectly with eth0=slirp and eth1=tuntp.

/etc/conf.d/net had:
config_eth0=( "dchp" )
config_eth1=( "192.168.37.20/24" )

I could ssh to the colinux layer via eth1 and use portage successfully 
on eth0.

Now portage has stopped working and I cannot ping google or access 
www.yahoo.com with lynx. The Tuntap connection to the XP layer remains 
intact.

I'm not sure what I might have done to disrupt the eth0 service. I have 
installed apache, but turning apache off does not help.

Can anyone think of anything I can check?

ifconfig tells me:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

eth0      Link encap:Ethernet  HWaddr 00:FF:E8:32:BD:00
          inet addr:10.0.2.15  Bcast:10.0.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:25 errors:0 dropped:0 overruns:0 frame:0
          TX packets:189 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1050 (1.0 Kb)  TX bytes:14282 (13.9 Kb)
          Interrupt:2

eth1      Link encap:Ethernet  HWaddr 00:FF:F9:56:80:00
          inet addr:192.168.37.20  Bcast:192.168.37.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:372 errors:0 dropped:0 overruns:0 frame:0
          TX packets:498 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:29783 (29.0 Kb)  TX bytes:69384 (67.7 Kb)
          Interrupt:2

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

(I had my old laptop stolen in a burglary and I'm trying to set up the 
replacement)

Re: [coLinux-users] Problems with cofs and .c Files : error: stray '\240'

[Tiago J. <tia...@ya...>]

Henry Nestler wrote:
>
> The gcc internalny use 'mmap' to map your file into memory instead to 
> read the file directly. Some times gcc reads behind the end of file, so 
> you gets errors behid your last line of source file.
>
> The bug results from 'fstab' on cofs device, that comes to fast after 
> last write operation on the same file or directory.
>
> I'm not remember, but there exist a parameter for gcc to disable the 
> mapping source files into memory via 'mmap' and simple use only "open - 
> read - close" for reading source files.
>
>   
Yes, I can disable mmap with gcc parameter --disable-mmap. I need to 
recompile my buildroot with this option, and this will take me a time.
If I have any progress, i will post here.


Tks

Tiago Jost

		
_______________________________________________________ 
Yahoo! Mail - Sempre a melhor opção para você! 
Experimente já e veja as novidades. 
http://br.yahoo.com/mailbeta/tudonovo/
 

Re: [coLinux-users] Problems with cofs and .c Files : error: stray '\240'

[Henry N. <Hen...@Ar...>]

Tiago Jost wrote:
> Hi.
> 
> First, sorry for my english. I´m working to make it better.
> Now,  my problem:
> I´m using coLinux to port a uClibC buildroot. It´s working fine, and i 
> can compile my arm9 programs just like I do in Suse 10, with the same 
> speed, if I copy all the files of my project  from windows partition 
> inside the environment, like /home/user/Project.
> 
> If I just mount the Windows partition, and try to compile the project 
> inside the mount point (like /mnt/win/c/Project), I got errors, on some 
> files, like:
> crypt.*c*:1350: *error*: *stray* '\240' in program
> 
> But the c file have just 1350 lines , for example, and the errors continue

The gcc internalny use 'mmap' to map your file into memory instead to 
read the file directly. Some times gcc reads behind the end of file, so 
you gets errors behid your last line of source file.

The bug results from 'fstab' on cofs device, that comes to fast after 
last write operation on the same file or directory.

I'm not remember, but there exist a parameter for gcc to disable the 
mapping source files into memory via 'mmap' and simple use only "open - 
read - close" for reading source files.

--
Henry

[coLinux-users] Problems with cofs and .c Files : error: stray '\240'

[Tiago J. <tia...@ya...>]

Hi.

First, sorry for my english. I´m working to make it better.
Now,  my problem:
I´m using coLinux to port a uClibC buildroot. It´s working fine, and i 
can compile my arm9 programs just like I do in Suse 10, with the same 
speed, if I copy all the files of my project  from windows partition 
inside the environment, like /home/user/Project.

If I just mount the Windows partition, and try to compile the project 
inside the mount point (like /mnt/win/c/Project), I got errors, on some 
files, like:
crypt.*c*:1350: *error*: *stray* '\240' in program

But the c file have just 1350 lines , for example, and the errors continue

crypt.*c*:1351: *error*: *stray* '\130' in program

I think that it was a problem with encode type or line delimiters, then 
I compare the files with error and the files without error in a hex 
edit, and both are ok.

Then, I start a new file with code, and compile it every 100 lines. It 
goes ok in the first 3 times, and when the program was with ~400 lines, 
the same errors occurs again.
I compare the files in my project, and in fact, this only happens in 
files with more than 400 lines (I don´t know the file size, I will check 
it, think that the size is the problem).

I test with coLinux+ArchLinux and andLinux.

To "solve" my problem, I now mount the Windows hd with smbmount, and the 
error don´t occur.
My windows filesystem is NTFS, and I try the same with a PenDrive

Does anybody have a similar problem and can help-me?

Thanks.


Tiago Jost


	

	
		
_______________________________________________________ 
Yahoo! Mail - Sempre a melhor opção para você! 
Experimente já e veja as novidades. 
http://br.yahoo.com/mailbeta/tudonovo/