You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(100) |
Jun
(134) |
Jul
(149) |
Aug
(123) |
Sep
(185) |
Oct
(122) |
Nov
(59) |
Dec
(127) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(128) |
Feb
(233) |
Mar
(210) |
Apr
(196) |
May
(85) |
Jun
(96) |
Jul
(76) |
Aug
(149) |
Sep
(65) |
Oct
(78) |
Nov
(121) |
Dec
(82) |
2006 |
Jan
(249) |
Feb
(181) |
Mar
(176) |
Apr
(156) |
May
(128) |
Jun
(102) |
Jul
(157) |
Aug
(80) |
Sep
(42) |
Oct
(49) |
Nov
(36) |
Dec
(42) |
2007 |
Jan
(64) |
Feb
(38) |
Mar
(45) |
Apr
(74) |
May
(26) |
Jun
(20) |
Jul
(17) |
Aug
(12) |
Sep
(40) |
Oct
(7) |
Nov
(14) |
Dec
(16) |
2008 |
Jan
(52) |
Feb
(49) |
Mar
(90) |
Apr
(80) |
May
(78) |
Jun
(82) |
Jul
(25) |
Aug
(8) |
Sep
(10) |
Oct
(11) |
Nov
(3) |
Dec
(17) |
2009 |
Jan
(12) |
Feb
(16) |
Mar
(20) |
Apr
(14) |
May
(17) |
Jun
(10) |
Jul
(13) |
Aug
(12) |
Sep
(21) |
Oct
(10) |
Nov
(30) |
Dec
(1) |
2010 |
Jan
(2) |
Feb
(7) |
Mar
(22) |
Apr
(6) |
May
(33) |
Jun
(5) |
Jul
(4) |
Aug
(38) |
Sep
(46) |
Oct
(23) |
Nov
(9) |
Dec
(5) |
2011 |
Jan
(21) |
Feb
(27) |
Mar
(1) |
Apr
(18) |
May
(12) |
Jun
(12) |
Jul
(10) |
Aug
(30) |
Sep
(4) |
Oct
|
Nov
(9) |
Dec
(19) |
2012 |
Jan
(26) |
Feb
(6) |
Mar
(8) |
Apr
(7) |
May
(3) |
Jun
|
Jul
(10) |
Aug
(1) |
Sep
(18) |
Oct
(5) |
Nov
|
Dec
(1) |
2013 |
Jan
(27) |
Feb
|
Mar
(11) |
Apr
(14) |
May
|
Jun
(1) |
Jul
|
Aug
(7) |
Sep
|
Oct
(1) |
Nov
(2) |
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
(25) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
(2) |
Dec
|
2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Ferry T. <ft...@te...> - 2009-11-04 15:28:10
|
On your questions below: - I had 128MB RAM + 256MB swap file. Changed that to 200MB RAM + 256MB swap. No performance improvement. - Yes, X11 goes over TAP, SLiRP is disabled, I have a bridged (pcap) connection for all the other routes then to the windows host. - the hostname was not present in the /etc/hosts file, add that per your comment, no performance improvement Note once again: if I start xclock it starts within 0.5sec. If I start gedit it can take 5 - 10 sec. The real annoyance is with evolution, as switching from 1 mail folder to another, or from mail to calendar can take 5 - 10 seconds. Worse, click create a new e-mail button take 5 - 10 seconds for the new window to appear. It seems the problem is caused mainly on new window creations for/from a gnome application. My .conf file: ---- kernel=vmlinux cobd0=images\rootfs.img #cobd3=images\rootfs_.img cofs0=config cofs1=c:\ root=/dev/cobd0 ro initrd=initrd.gz mem=200 eth0=pcap-bridge,"LAN-verbinding",0A:C0:71:65:08:01 eth1=tuntap,"Pubuntu-TAP",0A:C0:71:65:08:00 exec0="C:\Program Files\Xming\Xming.exe :0 -notrayicon -ac -wm -clipboard -multiwindow -dpi 100 -xkblayout us -xkbmodel pc105" exec1=pulseaudio-0.9.6\pulseaudio.exe -- Ferry Toth <ft...@te...> -----Oorspronkelijke bericht----- Van: Henry Nestler <hen...@ar...> Aan: Ferry Toth <ft...@te...> Cc: col...@li... Onderwerp: Re: Slow response - CPU load low Datum: Wed, 28 Oct 2009 23:13:28 +0100 Nieuwsgroepen: gmane.linux.colinux.general Ferry Toth wrote: > I have got the latest colinux snapshot, Ubuntu jaunty up to date, > network connection with pcap and tap device (both 100Mbs), and bought > a license to XMIng. > > And all is working fine... except: > > Opening a window to a new program (evolution, gedit) is incredibly > slow. It can take like 10 seconds. However, starting xclock, no > problem within a second. > > Now, I can wait for an app to start, but with evolution switching from > mail to organizer to adres book is just as slow. > > Strangely: during the slowness the CPU load on the host is low, the > CPU load on the pubuntu is low, there is very little network traffic. > > And my Ubuntu clock nicely ticks away the seconds on screen, so clock, > connection are all working fine. > > What the ... is colinux doing during this long pause? Or is there a > problem in my configuration? You should post your configuration (Windows side), so we can check it. Check your free memory with "free" under Linux. Try to give more memory to the coLinux with the config option "mem=..." (in Megabytes). Add a swap file, if you have not enough memory. Check your network configuration, that X11 truely goes over TAP-Win32 and not some wired ways over SLiRP and/or your local network. Disable temporally your SLiRP or Bridged things, in the coLinux config on Windows or by calling "ifconfig eth0 down" under Linux. Remove temporally your network cable from Windows. Than check the performance again. Or boot Windwos without network and check the launch speed. Check your name resolution (DNS). Check, that the coLinux "hostname" is listed in the file /etc/hosts with the ipaddress of tap on the Linux side, and also with an other name and ip for the TAP-Win32 side. For example: 192.168.0.1 windows 192.168.0.2 colinux The real names for Windows does not matter, but you must use your ip addresses there. Some programs tries to resolve back the ipaddress to a hostname, and if you don't have a real DNS-Server for the TAP addresses, this can be timeout you have seen. -- Henry N. ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ coLinux-users mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-users |
From: Henry N. <hen...@ar...> - 2009-11-04 10:17:13
|
Hello Peter, many thanks for all details! Peter Kuznetsov wrote: > [...snip...] > Linux version 2.6.25.20-co-0.8.0 (hn@hn-dt) (gcc version 4.2.1 (SUSE Linux)) #4 PREEMPT Tue Nov 3 22:53:46 CET 2009 > Ok. I see, you used that version. > [...snip...] > Kernel panic - not syncing: COSCSI: response: use_sg (2)> 1! > and I'm totaly not understand how this text can print. Because the string "COSCSI: response: use_sg" have removed. So I have checked the source again, and found, that I have changed the function "host_pass()", that have similar code, instead to change the function "response()". *BIG SORRY FROM ME!* Here is a new build "#6 PREEMPT Wed Nov 4 11:07:09 CET 2009": http://www.henrynestler.com/colinux/testing/devel-0.8.0/20091104-scsi/ vmlinux-2.6.25.20-co-0.8.0-20091104.zip -- Henry N. |
From: Peter K. <pet...@ma...> - 2009-11-04 07:17:45
|
Henry Nestler wrote: > Please try to start colinux-daemon from normal windows command prompt (CMD.EXE), not inside a Cygwin shell. I execute all my programs from 'Far File Menager' by Eugene Roshal. Henry Nestler wrote: > Perhaps "kernel=vmlinux" in the config points to an other directory of the file "vmlinux"? When I recieved your letter, I've did next steps: 1. Renamed vmlinux to vmlinux_new. 2. Executed "run.bat" from Start->Run with path "Q:\coLinux\$Debian\Debian\Debian-5.0.3-err_SCSI\run.bat" and recived next full output (copied from console window to clipboard after kernel panic): Q:\coLinux\$Debian\Debian\Debian-5.0.3-err_SCSI>set COLINUX_CONSOLE_FONT=Lucida Console:12 Q:\coLinux\$Debian\Debian\Debian-5.0.3-err_SCSI>set COLINUX_CONSOLE_EXIT_ON_DETACH=1 Q:\coLinux\$Debian\Debian\Debian-5.0.3-err_SCSI>colinux-daemon.exe --remove-driver Cooperative Linux Daemon, 0.8.0 Daemon compiled on Sun Sep 27 12:50:20 2009 driver not installed Q:\coLinux\$Debian\Debian\Debian-5.0.3-err_SCSI>colinux-daemon.exe --install-driver Cooperative Linux Daemon, 0.8.0 Daemon compiled on Sun Sep 27 12:50:20 2009 loading Q:\coLinux\$Debian\Debian\Debian-5.0.3-err_SCSI\linux.sys daemon: driver installed Q:\coLinux\$Debian\Debian\Debian-5.0.3-err_SCSI>colinux-daemon.exe @config.cfg -v 3 -t nt Cooperative Linux Daemon, 0.8.0 Daemon compiled on Sun Sep 27 12:50:20 2009 using 'vmlinux_new' as kernel image configuring 512 MB of virtual RAM scsi0: disk -> \??\Q:\coLinux\$Debian\Debian\Debian-5.0.3-err_SCSI\Debian-5.0.3-KDE-00.flat (size: 0 MB) scsi1: cdrom -> \??\J:\OS\Linux\$DEBIAN\Debian\5.0.3\debian-503-i386-DVD-1.iso (size: 0 MB) configured Slirp as eth0 using 'initrd.gz' as initrd image mapping cofs31 to \??\Q:\coLinux\$Debian\Debian\Debian-5.0.3-err_SCSI kernel boot parameters: 'root=/dev/sda1 ro' eth0: MAC found in registry: 00:ff:fb:34:80:00 PID: 5016 colinux: launching console colinux: booting console: Cooperative Linux console started conet-slirp-daemon: running Linux version 2.6.25.20-co-0.8.0 (hn@hn-dt) (gcc version 4.2.1 (SUSE Linux)) #4 PREEMPT Tue Nov 3 22:53:46 CET 2009 512MB LOWMEM available. initrd enabled: 0xdff9a000-0xdffff881 size: 0x00065881 Entering add_active_range(0, 0, 131072) 0 entries of 256 used Zone PFN ranges: Normal 0 -> 131072 Movable zone start PFN for each node early_node_map[1] active PFN ranges 0: 0 -> 131072 On node 0 totalpages: 131072 Normal zone: 1024 pages used for memmap Normal zone: 0 pages reserved Normal zone: 130048 pages, LIFO batch:31 Movable zone: 0 pages used for memmap Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 Kernel command line: root=/dev/sda1 ro Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 Setting proxy interrupt vectors PID hash table entries: 2048 (order: 11, 8192 bytes) Console: colour CoCON 160x79 console [tty0] enabled Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 514944k/524288k available (2029k kernel code, 0k reserved, 618k data, 156k init, 0k highmem) virtual kernel memory layout: fixmap : 0xffffa000 - 0xfffff000 ( 20 kB) vmalloc : 0xe0800000 - 0xffff8000 ( 503 MB) lowmem : 0xc0000000 - 0xe0000000 ( 512 MB) .init : 0xcCPA: page pool initialized 1 of 1 pages preallocated Calibrating delay loop... 8781.82 BogoMIPS (lpj=43909120) Security Framework initialized SELinux: Disabled at boot. Capability LSM initialized Mount-cache hash table entries: 512 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 3072K using mwait in idle threads. Compat vDSO mapped to ffffe000. CPU: Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz stepping 0a Checking 'hlt' instruction... OK. Freeing SMP alternatives: 0k freed net_namespace: 536 bytes NET: Registered protocol family 16 SCSI subsystem initialized PCI: Probing PCI hardware PCI: Probing PCI hardware (bus 00) NET: Registered protocol family 2 IP route cache hash table entries: 16384 (order: 4, 65536 bytes) TCP established hash table entries: 65536 (order: 7, 524288 bytes) TCP bind hash table entries: 65536 (order: 6, 262144 bytes) TCP: Hash tables configured (established 65536 bind 65536) TCP reno registered checking if image is initramfs...it isn't (no cpio magic); looks like an initrd Freeing initrd memory: 406k freed audit: initializing netlink socket (disabled) type=2000 audit(1257317778.620:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) cofuse init 0.1 (API version 2.2) io scheduler noop registered io scheduler anticipatory registered (default) io scheduler deadline registered io scheduler cfq registered brd: module loaded cobd: loaded (max 32 devices) loop: module loaded conet0: irq 10, HWAddr 00:ff:fb:34:80:00 scsi0 : Cooperative Linux SCSI Adapter scsi 0:0:0:0: Direct-Access coLinux CODISK 1.01 PQ: 0 ANSI: 5 scsi 0:0:1:0: CD-ROM coLinux COCD 1.01 PQ: 0 ANSI: 2 Driver 'sd' needs updating - please use bus_type methods sd 0:0:0:0: [sda] 6291456 512-byte hardware sectors (3221 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA sd 0:0:0:0: [sda] 6291456 512-byte hardware sectors (3221 MB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 1f 00 10 08 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA sda: sda1 sd 0:0:0:0: [sda] Attached SCSI disk Driver 'sr' needs updating - please use bus_type methods sr0: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.20 sr 0:0:1:0: Attached scsi CD-ROM sr0 serio: cokbd at irq 1 mice: PS/2 mouse device common for all mice TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 Using IPI Shortcut mode input: AT Translated Set 2 keyboard as /devices/serio0/input/input0 RAMDISK: Compressed image found at block 0 VFS: Mounted root (ext2 filesystem). ReiserFS: sda1: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on sda1 EXT3-fs: INFO: recovery required on readonly filesystem. EXT3-fs: write access will be enabled during recovery. kjournald starting. Commit interval 5 seconds EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. Trying to move old root to /initrd ... /initrd does not exist. Ignored. Unmounting old root Trying to free ramdisk memory ... okay Freeing unused kernel memory: 156k freed scsi1: unhandled opcode: 51 sd 0:0:0:0: Attached scsi generic sg0 type 0 sr 0:0:1:0: Attached scsi generic sg1 type 5 scsi1: unhandled opcode: 51 EXT3 FS on sda1, internal journal NET: Registered protocol family 10 lo: Disabled Privacy Extensions Kernel panic - not syncing: COSCSI: response: use_sg (2) > 1! colinux: Linux VM terminated colinux: Kernel panic: COSCSI: response: use_sg (2) > 1! Q:\coLinux\$Debian\Debian\Debian-5.0.3-err_SCSI>colinux-daemon.exe --remove-driver Cooperative Linux Daemon, 0.8.0 Daemon compiled on Sun Sep 27 12:50:20 2009 console: Monitor5016: Detached Q:\coLinux\$Debian\Debian\Debian-5.0.3-err_SCSI>pause Press any key to continue . . . --------------------------------------------------------------------------------- Directory (Cygwin 'dir' started from from Far): Q:\coLinux\$Debian\Debian\Debian-5.0.3-err_SCSI>dir -l total 3153066 -rwx------+ 1 peter None 3221225472 Nov 4 08:56 Debian-5.0.3-KDE-00.flat -rwx------+ 1 peter None 109056 Sep 27 15:50 colinux-console-nt.exe -rwx------+ 1 peter None 102912 Sep 27 15:50 colinux-daemon.exe -rwx------+ 1 peter None 46592 Sep 27 15:50 colinux-ndis-net-daemon.exe -rwx------+ 1 peter None 100864 Sep 27 15:50 colinux-net-daemon.exe -rwx------+ 1 peter None 97792 Sep 27 15:50 colinux-slirp-net-daemon.exe -rwx------+ 1 peter None 275 Nov 4 08:46 config.cfg -rwx------+ 1 peter None 415873 Aug 31 2006 initrd.gz -rwx------+ 1 peter None 82432 Sep 27 15:50 linux.sys -rwx------+ 1 peter None 241 Nov 4 08:55 run.bat -rwx------+ 1 peter None 2669547 Sep 27 15:50 vmlinux-modules.tar.gz -rwx------+ 1 peter None 3868534 Nov 3 22:53 vmlinux_new ----------------------------------------------------------------------------------- run.bat: set COLINUX_CONSOLE_FONT=Lucida Console:12 set COLINUX_CONSOLE_EXIT_ON_DETACH=1 colinux-daemon.exe --remove-driver colinux-daemon.exe --install-driver colinux-daemon.exe @config.cfg -v 3 -t nt colinux-daemon.exe --remove-driver pause ----------------------------------------------------------------------------------- config.cfg: cocon=160x79 mem=512 kernel=vmlinux_new initrd=initrd.gz scsi0=disk,"Debian-5.0.3-KDE-00.flat" scsi1=cdrom,"J:\OS\Linux\$DEBIAN\Debian\5.0.3\debian-503-i386-DVD-1.iso" # <---- this causes error! root=/dev/sda1 ro eth0=slirp =================================================================================== Ok, I've tried almost all images from sourceforge.net and all of them works. Then I've packed the image in question to archive "Debian-5.0.3-err_SCSI.tar.bz2". But it is big - about 920 Mb. Unpacked size of the image is 3 Gb. I've installed mini-version of Debian-5.0.3 on 1 Gb image (actual size is about 300 Kb) but it works without SCSI error! So, if you can give me address of a site, I'll upload "Debian-5.0.3-err_SCSI.tar.bz2" and you can reproduce this error. If you want, you may send me private message with URL. Peter. |
From: Peter K. <pet...@ma...> - 2009-11-04 01:58:09
|
-----Original Message----- From: Peter Kuznetsov <pet...@ma...> To: Henry Nestler <hen...@ar...> Date: Wed, 04 Nov 2009 04:52:51 +0300 Subject: Re[2]: [coLinux-users] coLinux error in SCSI-driver with DVD-image > > > > Hello Peter, > > > > Peter Kuznetsov wrote: > > > Kernel panic - not syncing: COSCSI: response: use_sg (2)> 1! > > > > > > > Please install the latest snapshot (2009-09-27) from > > http://www.colinux.org/snapshots/ or > > http://www.henrynestler.com/colinux/testing/devel-0.8.0/20090927-Snapshot/packages/ > > > > Than replace vmlinux with the file from > > http://www.henrynestler.com/colinux/testing/devel-0.8.0/20091103-scsi/ > > > > There the kernel should print a caller stack for this bug. > > > > -- > > Henry N. > > > > If linux-2.6.25.20-source/drivers/scsi/coscsi.c was compiled as module, I need /lib/modules/2.6.25.20-co-0.8.0/kernel/drivers/scsi/* also, because your patched driver is located there. Peter |
From: Henry N. <hen...@ar...> - 2009-11-03 22:13:16
|
Hello Peter, Peter Kuznetsov wrote: > Kernel panic - not syncing: COSCSI: response: use_sg (2)> 1! > Please install the latest snapshot (2009-09-27) from http://www.colinux.org/snapshots/ or http://www.henrynestler.com/colinux/testing/devel-0.8.0/20090927-Snapshot/packages/ Than replace vmlinux with the file from http://www.henrynestler.com/colinux/testing/devel-0.8.0/20091103-scsi/ There the kernel should print a caller stack for this bug. -- Henry N. |
From: Henry N. <hen...@ar...> - 2009-11-03 21:48:25
|
hello Peter, Peter Kuznetsov wrote: > What does it mean next coLinux messages? > > scsi2: unhandled opcode: 51 > scsi2: unhandled opcode: 5a > Driver 'sd' needs updating - please use bus_type methods > Driver 'sr' needs updating - please use bus_type methods > Kernel panic - not syncing: COSCSI: response: use_sg (2)> 1! > > See the post at https://sourceforge.net/tracker/?func=detail&aid=2890857&group_id=98788&atid=622063 > It would be nice to see this bug in my installation. But, it does running without problems for me. My coLinux config: colinux-daemon -t nt mem=64 kernel=vmlinux ^ cobd0=Debian-4.0.img root=/dev/cobd0 ^ cofs0=. ^ scsi0=cdrom,\Device\Cdrom0 "\Device\Cdrom0" is a Fedora 10 install DVD. This I used to checksum the read via scsi driver. Under Linux was running: debian:~# dd if=/dev/sr0 | md5sum 27e581edb392728c4a07d00d3fc5ced0 - 7153464+0 records in 7153464+0 records out 3662573568 bytes (3.7 GB) copied, 797.93 seconds, 4.6 MB/s But, have not your messages in kernel logs. debian:~# dmesg | grep -E 'sr|sd|scsi' scsi0 : Cooperative Linux SCSI Adapter scsi 0:0:1:0: CD-ROM coLinux COCD 1.01 PQ: 0 ANSI: 2 Driver 'sd' needs updating - please use bus_type methods Driver 'sr' needs updating - please use bus_type methods sr0: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray sr 0:0:1:0: Attached scsi CD-ROM sr0 My used coLinux was the last snapshot from http://www.colinux.org/snapshots/ : debian:~# dmesg | head -n1 Linux version 2.6.25.20-co-0.8.0 (hn@hn-dt) (gcc version 4.2.1 (SUSE Linux)) #2 PREEMPT Sun Sep 27 12:49:54 UTC 2009 -- Henry N. |
From: Peter K. <pet...@ma...> - 2009-11-03 15:30:32
|
What does it mean next coLinux messages? scsi2: unhandled opcode: 51 scsi2: unhandled opcode: 5a Driver 'sd' needs updating - please use bus_type methods Driver 'sr' needs updating - please use bus_type methods Kernel panic - not syncing: COSCSI: response: use_sg (2) > 1! See the post at https://sourceforge.net/tracker/?func=detail&aid=2890857&group_id=98788&atid=622063 Thanks, Peter |
From: Frédéric L. W. M. <lis...@pe...> - 2009-11-03 05:11:13
|
I'm curious about what the following means. I looked in my logs, and there are those occurences: In 2007, running XP SP2: Dec 1 15:49:21 pervalidus kernel: Linux version 2.6.22-co-0.8.0 (henryn@gcc11)(gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 PREEMPT Wed Nov 28 05:09:28 UTC 2007 Dec 1 17:15:00 pervalidus kernel: fuse_dir_open: host returned error: fffffffe Dec 1 17:15:41 pervalidus kernel: fuse_dir_open: host returned error: fffffffe In 2009, running Vista SP1: Mar 27 14:29:10 pervalidus kernel: Linux version 2.6.22.18-co-0.8.0 (henryn@gcc11) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 PREEMPT Thu Mar 5 05:08:03 UTC 2009 Apr 10 18:00:21 pervalidus kernel: fuse_dir_open: host returned error: ffffffff Apr 10 18:00:28 pervalidus last message repeated 65 times In 2009, running 7: Nov 2 15:33:26 pervalidus kernel: Linux version 2.6.25.20-co-0.8.0 (henryn@gcc16) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #2 PREEMPT Sat Sep 26 04:10:43 UTC 2009 Nov 3 01:00:11 pervalidus kernel: fuse_dir_open: host returned error: ffffffff Nov 3 01:00:13 pervalidus last message repeated 49 times So, this looks very rare. There's also this, which appears more times (around 25) Nov 2 15:34:17 pervalidus kernel: cofuse: unsuppored request 6 BTW, it should be unsupporTed. |
From: Frank C. <vfc...@go...> - 2009-11-02 17:06:35
|
2009/10/14 H. Nestler <hen...@ar...>: > Josep Maria Antolín Segura wrote: >> >> While you say you've disabled the firewall.. did you do so on the Windows' >> one? >> >> Other than that, your configuration seems file, more so if you can >> establish >> connection with colinux. >> You could also try not putting a name on the tuntap adapter (i.e., remove >> "TAP"). If you only have one, the name is optional. It is necessary when >> there >> are more than one (case of multiple colinux running simultaneously). If >> this fixes it, then the name indicated is incorrect. >> >> >> At last, your X notions are correct. your DISPLAY var would be >> DISPLAY=192.168.2.1:0.0 , and then you have to configure xming to not use >> access control. (allows connections from any ip). > > Disabling "access control" you does by adding "-ac" to the command line for Xming. > > Additional I would ask you to check, that you don't have non other adapters in the network 192.168.2.xxx > > As I see, that you also have eth0 with the pcap-bridge, you can also use the ip adress from your real Ethernet adapter, and put it's ip address into the DISPLAY variable. > > As you say, ssh into coLinux does work, than do follow steps: > Login with SSH > Check the ip of host with command "set | grep SSH_CLIENT" > Use this ip address from above in the DISPLAY > Call for example "DISPLAY=192.168.2.1:0.0 xterm" > > > -- > Henry > > --------------------------------------------------------- > ... Es folgt Arcor Werbung | Ads follows by Arcor ... > > > Comedy-Battle! Jetzt ablachen und voten! Neue Comedians, Spontanhumoristen und Nachwuchs-Spaßmacher machen gute Laune - bestimmen Sie den Wochensieger! > http://comedy-battle.arcor.de/ > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > Check if the problem may be due to Tcp/IP Checksum Offloading problem described in http://colinux.wikia.com/wiki/Network. I have experienced a similar problem recently -- Frank Church ======================= http://devblog.brahmancreations.com |
From: Frank C. <vfc...@go...> - 2009-11-02 17:03:31
|
2009/11/2 Frank Church <vfc...@go...>: > My system crashed so I reinstalled windows and colinux with the > settings as they were before. > > However although Windows can connect to coLinux and they can both ping > each other, windows is not receiving responses from coLinux. I have > tried connecting to the colinux apache service and ssh server with > putty, but there is no response. > > colinux can also retrieve data from the internet through the router just fine. > > This is the configuration in use, and it worked fine before I had to reinstall > > eth0=pcap-bridge,"System Network Bridge" > eth1=pcap-bridge,"Local Area Connection" > > The System Network Bridge is not really in use and I don't think > disabling that should make a difference. > > > -- > Frank Church > > ======================= > <a href="http://devblog.brahmancreations.com">devblog.brahmancreations.com</a> > After doing some reading it turns out the problem was due to Tcp/IP Checksum Offloading problem described in http://colinux.wikia.com/wiki/Network. I new driver I downloaded had that option configured. -- Frank Church ======================= http://devblog.brahmancreations.com |
From: Frank C. <vfc...@go...> - 2009-11-02 15:41:23
|
My system crashed so I reinstalled windows and colinux with the settings as they were before. However although Windows can connect to coLinux and they can both ping each other, windows is not receiving responses from coLinux. I have tried connecting to the colinux apache service and ssh server with putty, but there is no response. colinux can also retrieve data from the internet through the router just fine. This is the configuration in use, and it worked fine before I had to reinstall eth0=pcap-bridge,"System Network Bridge" eth1=pcap-bridge,"Local Area Connection" The System Network Bridge is not really in use and I don't think disabling that should make a difference. -- Frank Church ======================= <a href="http://devblog.brahmancreations.com">devblog.brahmancreations.com</a> |
From: Henry N. <hen...@ar...> - 2009-10-31 02:11:46
|
mat tag wrote: > I am currently trying to use colinux with 2Go of RAM, for running > scientific applications; but I get quite the same thing as in this old > post here : > http://thread.gmane.org/gmane.linux.colinux.general/1515/focus=1516 > > The output of the log requested at that time, and obtained by running > colinux-debug-daemon.exe -d -p -s prints=255,misc=255> msg.log > > is : > > > <log module="colinux-driver" file="src/colinux/kernel/monitor.c" > timestamp="00000001.1102917059" local_index="13" facility="0" > function="co_monitor_create" line="1084" level="10" driver_index="129"> > <string>_configured to 2048 MB_</string> > </log> > <log module="colinux-driver" file="src/colinux/kernel/monitor.c" > timestamp="00000001.1102917246" local_index="14" facility="0" > function="co_monitor_create" line="1091" level="10" driver_index="130"> > <string>_after adjustments: 1000 MB_</string> > </log> > > Basically, it seems that the systems decides to allocate 1go of RAM > while I was asking for 2. Is there a known workaround? No workaround available. The current kernel source supports only "low memory" and this limit is some bytes under 1GB (24 MB are uses for page tables). -- Henry N. |
From: mat t. <ta...@ho...> - 2009-10-30 14:04:31
|
Hi everyone! I am currently trying to use colinux with 2Go of RAM, for running scientific applications; but I get quite the same thing as in this old post here : http://thread.gmane.org/gmane.linux.colinux.general/1515/focus=1516 The output of the log requested at that time, and obtained by running colinux-debug-daemon.exe -d -p -s prints=255,misc=255 > msg.log is : <log module="colinux-driver" file="src/colinux/kernel/monitor.c" timestamp="00000001.1102917059" local_index="13" facility="0" function="co_monitor_create" line="1084" level="10" driver_index="129"> <string>configured to 2048 MB</string> </log> <log module="colinux-driver" file="src/colinux/kernel/monitor.c" timestamp="00000001.1102917246" local_index="14" facility="0" function="co_monitor_create" line="1091" level="10" driver_index="130"> <string>after adjustments: 1000 MB</string> </log> Basically, it seems that the systems decides to allocate 1go of RAM while I was asking for 2. Is there a known workaround? Thanks in advance Tag _________________________________________________________________ Windows Live: Friends get your Flickr, Yelp, and Digg updates when they e-mail you. http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_3:092010 |
From: Henry N. <hen...@ar...> - 2009-10-28 22:12:29
|
Ferry Toth wrote: > I have got the latest colinux snapshot, Ubuntu jaunty up to date, > network connection with pcap and tap device (both 100Mbs), and bought > a license to XMIng. > > And all is working fine... except: > > Opening a window to a new program (evolution, gedit) is incredibly > slow. It can take like 10 seconds. However, starting xclock, no > problem within a second. > > Now, I can wait for an app to start, but with evolution switching from > mail to organizer to adres book is just as slow. > > Strangely: during the slowness the CPU load on the host is low, the > CPU load on the pubuntu is low, there is very little network traffic. > > And my Ubuntu clock nicely ticks away the seconds on screen, so clock, > connection are all working fine. > > What the ... is colinux doing during this long pause? Or is there a > problem in my configuration? You should post your configuration (Windows side), so we can check it. Check your free memory with "free" under Linux. Try to give more memory to the coLinux with the config option "mem=..." (in Megabytes). Add a swap file, if you have not enough memory. Check your network configuration, that X11 truely goes over TAP-Win32 and not some wired ways over SLiRP and/or your local network. Disable temporally your SLiRP or Bridged things, in the coLinux config on Windows or by calling "ifconfig eth0 down" under Linux. Remove temporally your network cable from Windows. Than check the performance again. Or boot Windwos without network and check the launch speed. Check your name resolution (DNS). Check, that the coLinux "hostname" is listed in the file /etc/hosts with the ipaddress of tap on the Linux side, and also with an other name and ip for the TAP-Win32 side. For example: 192.168.0.1 windows 192.168.0.2 colinux The real names for Windows does not matter, but you must use your ip addresses there. Some programs tries to resolve back the ipaddress to a hostname, and if you don't have a real DNS-Server for the TAP addresses, this can be timeout you have seen. -- Henry N. |
From: Henry N. <hen...@ar...> - 2009-10-28 20:54:50
|
Cooperative Linux version 0.7.5 was released now. Release: 0.7.5 Kernel: 2.6.22.18 Build date: 15-September-2009 This is a bugfix release. Please check the project file release and wiki for information, updates and progress. Downloads: http://sourceforge.net/projects/colinux/files/coLinux-stable/0.7.5-linux-2.6.22.18 ChangeLog: http://www.colinux.org/?section=status Wiki: http://colinux.wikia.com Snapshots: http://www.colinux.org/snapshots ---- NEWS General: * Bug #1959846, #2760666: Don't crash the host, if an other virtualization runs in VMX mode. Network: * Bug #2849262: SLiRP: Active FTP failed with "500 Illegal PORT command". Environment COLINUX_HOST_IPADDR overwrites auto detected host ip address. Console and daemons: * Insert keys from fltk console without keyboard mapping. (Paolo Minazzi) * New: NT console WinKey+V paste keys from clipboard. (Vladislav Grishenko) * Linux as host: Handle extended keys, for example ALT+CurRight. * Automatically add network dependency to coLinux as service. * Version informations about binutils and SVN revision added to daemon file. Linux Kernel: * Remove floating point handling from passage page code. FPU save/restore only on demand and only inside Linux guest kernel, if Linux kernel or Linux userland needs the FPU. In cases where FPU was not used on Linux guest side, the registers of FPU are not touched. That saves some time between operating system switches. It's 1 percent (or less) faster now. * Increase CO_LINUX_API_VERSION to 13, avoids crashes with older builds. * cloop updated to version 2.625 * Forward plain text panic message instead "terminated with code 3". Buildsystem: * Bug #2847393: Configure detected wrong program versions. (Steven Chen) Updated libraries and tools: * w32api 3.13 -- Henry N. |
From: Ferry T. <ft...@te...> - 2009-10-27 16:15:27
|
Hi, I have got the latest colinux snapshot, Ubuntu jaunty up to date, network connection with pcap and tap device (both 100Mbs), and bought a license to XMIng. And all is working fine... except: Opening a window to a new program (evolution, gedit) is incredibly slow. It can take like 10 seconds. However, starting xclock, no problem within a second. Now, I can wait for an app to start, but with evolution switching from mail to organizer to adres book is just as slow. Strangely: during the slowness the CPU load on the host is low, the CPU load on the pubuntu is low, there is very little network traffic. And my Ubuntu clock nicely ticks away the seconds on screen, so clock, connection are all working fine. What the ... is colinux doing during this long pause? Or is there a problem in my configuration? All help welcome, Ferry |
From: H. N. <hen...@ar...> - 2009-10-14 21:51:48
|
Josep Maria Antolín Segura wrote: > > While you say you've disabled the firewall.. did you do so on the Windows' > one? > > Other than that, your configuration seems file, more so if you can > establish > connection with colinux. > You could also try not putting a name on the tuntap adapter (i.e., remove > "TAP"). If you only have one, the name is optional. It is necessary when > there > are more than one (case of multiple colinux running simultaneously). If > this fixes it, then the name indicated is incorrect. > > > At last, your X notions are correct. your DISPLAY var would be > DISPLAY=192.168.2.1:0.0 , and then you have to configure xming to not use > access control. (allows connections from any ip). Disabling "access control" you does by adding "-ac" to the command line for Xming. Additional I would ask you to check, that you don't have non other adapters in the network 192.168.2.xxx As I see, that you also have eth0 with the pcap-bridge, you can also use the ip adress from your real Ethernet adapter, and put it's ip address into the DISPLAY variable. As you say, ssh into coLinux does work, than do follow steps: Login with SSH Check the ip of host with command "set | grep SSH_CLIENT" Use this ip address from above in the DISPLAY Call for example "DISPLAY=192.168.2.1:0.0 xterm" -- Henry --------------------------------------------------------- ... Es folgt Arcor Werbung | Ads follows by Arcor ... Comedy-Battle! Jetzt ablachen und voten! Neue Comedians, Spontanhumoristen und Nachwuchs-Spaßmacher machen gute Laune - bestimmen Sie den Wochensieger! http://comedy-battle.arcor.de/ |
From: Josep M. A. S. <ja...@pa...> - 2009-10-14 17:49:47
|
While you say you've disabled the firewall.. did you do so on the Windows' one? Other than that, your configuration seems file, more so if you can establish connection with colinux. You could also try not putting a name on the tuntap adapter (i.e., remove "TAP"). If you only have one, the name is optional. It is necessary when there are more than one (case of multiple colinux running simultaneously). If this fixes it, then the name indicated is incorrect. At last, your X notions are correct. your DISPLAY var would be DISPLAY=192.168.2.1:0.0 , and then you have to configure xming to not use access control. (allows connections from any ip). If that didn't do, the SSH option will work, but generally it slows down the performance. |
From: Mark S. S. <bla...@gm...> - 2009-10-14 12:47:57
|
So I set up my networking to be like this: eth0=pcap-bridge,"Local Area Connection" eth1=tuntap,"TAP" TAP has an ip address of 192.168.2.1 /etc/network/interfaces contains: auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp auto eth1 iface eth1 inet static address 192.168.2.2 netmask 255.255.255.0 coLinux OS can ping sites and itself (192.168.2.2). I can also access 192.168.2.2 from windows. (i.e. I can ssh and view the webserver) But when I try to ping 192.168.2.1, I get nothing. When I checked on the adapter's status, it shows that it "receives" but it doesn't "send". Now this is frustrating because from what I've read, X needs to send to 192.168.2.1 so that Xming would display apps. BUT: VNC works. So I dunno. Maybe 192.168.2.1 is not what I'm supposed to use for DISPLAY and pinging? But all guides show that :( I tried turning off firewall and nameservers stuff... I first used a Debian 5 image and Xlaunch seemed to work (running an x program using plink) but not pinging to 192.168.2.1. With an Ubuntu 9.04 image, Xming reports it has 1 client but nothing shows up (I'm always trying to make xterm show up). I've also tried using Bebbo's configuration for networking but still no response from windows. |
From: H. N. <hen...@ar...> - 2009-10-10 20:51:05
|
vik wrote: > Is the coLinux support Windows Vista? The external link 'serbalinux.com - > openSuSE 10.3 on top of Vista' at henrynestler.com web page told it do. > But colinux.org web page omit these. It cite '...it allows one to freely > run Linux on Windows 2000/XP...'. The core needs update. Of curse coLinux runs on all Windows NT/2000/2003/2008/XP/Vista platforms. The only limit is 32 bit. Here is a set of screen shots from installing on Vista: http://www.henrynestler.com/colinux/screenshoots/Vista-Album/ Thanks for the point - update done. -- Henry --------------------------------------------------------- ... Es folgt Arcor Werbung | Ads follows by Arcor ... Comedy-Battle! Jetzt ablachen und voten! Neue Comedians, Spontanhumoristen und Nachwuchs-Spaßmacher machen gute Laune - bestimmen Sie den Wochensieger! http://comedy-battle.arcor.de/ |
From: <vi...@ch...> - 2009-10-10 16:22:25
|
Is the coLinux support Windows Vista? The external link 'serbalinux.com - openSuSE 10.3 on top of Vista' at henrynestler.com web page told it do. But colinux.org web page omit these. It cite '...it allows one to freely run Linux on Windows 2000/XP...'. The core needs update. |
From: Henry N. <hen...@ar...> - 2009-09-25 21:53:20
|
Eol wrote: > -Is it possible to hotplug a cobd device (linked to a windows file) > without changing the colinux Conf file ? > Yes, you can change everything on Windows host, if the cobd is not mounted inside Linux at same time. > -How can Colinux access to a USB mass storage or a USB dongle ? > The simplest way is cofs1=E:\ cofs2=F:\ and so on". -- Henry N. |
From: Eol <eol...@ho...> - 2009-09-25 07:52:24
|
Hi i have 2 questions : -Is it possible to hotplug a cobd device (linked to a windows file) without changing the colinux Conf file ? -How can Colinux access to a USB mass storage or a USB dongle ? Thx |
From: Henry N. <hen...@ar...> - 2009-09-15 07:25:14
|
Hello, Next release candidate 0.7.5-rc1 is available from snapshot page under "stable branch". http://www.colinux.org/snapshots/ This is a copy from currently branch devel. Users of devel 0.8.0 will not find any differences as only the versions number. Details about changes you can read from Changelog there. Here are the short news: * Version 0.7.5 * Bug #1959846, #2760666: Don't crash the host, if an other virtualization runs in VMX mode. Network: * Bug #2849262: SLiRP: Active FTP failed with "500 Illegal PORT command". Environment COLINUX_HOST_IPADDR overwrites auto detected host ip address. Console and daemons: * Insert keys from fltk console without keyboard mapping. (Paolo Minazzi) * New: NT console WinKey+V paste keys from clipboard. (Vladislav Grishenko) * Linux as host: Handle extended keys, for example ALT+CurRight. * Automatically add network dependency to coLinux as service. * Version informations about binutils and SVN revision added to daemon file. Kernel: * Remove floating point handling from passage page code. FPU save/restore only on demand and only inside Linux guest kernel, if Linux kernel or Linux userland needs the FPU. In cases where FPU was not used on Linux guest side, the registers of FPU are not touched. That saves some time between operating system switches. It's 1 percent (or less) faster now. * Increase CO_LINUX_API_VERSION to 13, avoids crashes with older builds. * cloop updated to version 2.625 * Forward plain text panic message instead "terminated with code 3". Buildsystem: * Bug #2847393: Configure detected wrong program versions. (Steven Chen) Updated libraries and tools: * w32api 3.13 -- Henry N. |
From: Henry N. <hen...@ar...> - 2009-09-14 20:28:48
|
Frank Church wrote: > I installed an ubuntu Gutsy and later upgraded them to Hardy Heron, > but it seems that some of the networking settings carried over, and as > I have to run them all at the same time I just want to make sure the > problems don't happen again. I am afraid to reboot them in case they > lose their settings. > > I have used the info in this link > http://colinux.wikia.com/wiki/Wubi#udev:_renamed_network_interface_eth0_to_eth2 > to fix the problem temporarily, but I am not sure what mac addresses > they will be given if I reboot them. I just want to have a way of > ensuring that the interfaces are given unique mac address when they > restart. > > These are the current ifconfig settings and the contents of the > /etc/udev/rules.d/70-persistent-net.rules, they are all derived from > the same image. > > > gutsy 7.1 - current configuration of ifconfig > ============================== > eth0 Link encap:Ethernet HWaddr 00:FF:41:48:88:00 > eth1 Link encap:Ethernet HWaddr 00:FF:37:1B:2C:00 > > <pre> > # This file maintains persistent names for network interfaces. > # See udev(7) for syntax. > # > # Entries are automatically added by the 75-persistent-net-generator.rules > # file; however you are also free to add your own entries. > > # PCI device 0x1a55:0x0005 (conet) > SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:ff:55:1d:81:00", > NAME="eth0" > > # PCI device 0x1a55:0x0005 (conet) > SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:ff:9c:6d:40:00", > NAME="eth1" > > [... snip...] > </pre> > > Remove them all. You can complete clean this file. You needs nothing of this entries. Do you have perhaps not changed the file "*-|persistent-net-generator.rules|" ? The "generator" of this stuff. The steps are: First edit the file "*-|persistent-net-generator.rules|" and add a bypass. Than remove all entries with "(conet)" from the file "*-persistent-net.rules". Than reboot. Or, if you wish to have fixed MAC for every time and for every user of your image, than add any of the MAC you have seen to the coLinux config file. Let start you self managed MAC with "02:ff:...". This way would need, if you switch the starts between command line running and "coLinux as service". -- Henry N. |