Menu
▾
▴
colinux-devel — Cooperative Linux development mailing list
You can subscribe to this list here.
| 2004 |
Jan
(64) |
Feb
(530) |
Mar
(266) |
Apr
(580) |
May
(360) |
Jun
(161) |
Jul
(185) |
Aug
(164) |
Sep
(123) |
Oct
(160) |
Nov
(59) |
Dec
(84) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(156) |
Feb
(95) |
Mar
(124) |
Apr
(81) |
May
(79) |
Jun
(179) |
Jul
(35) |
Aug
(64) |
Sep
(56) |
Oct
(57) |
Nov
(18) |
Dec
(41) |
| 2006 |
Jan
(65) |
Feb
(37) |
Mar
(59) |
Apr
(73) |
May
(65) |
Jun
(27) |
Jul
(54) |
Aug
(76) |
Sep
(103) |
Oct
(23) |
Nov
(45) |
Dec
(29) |
| 2007 |
Jan
(41) |
Feb
(47) |
Mar
(61) |
Apr
(24) |
May
(14) |
Jun
(6) |
Jul
(23) |
Aug
(30) |
Sep
(16) |
Oct
(9) |
Nov
(53) |
Dec
(36) |
| 2008 |
Jan
(19) |
Feb
(49) |
Mar
(74) |
Apr
(21) |
May
(24) |
Jun
(5) |
Jul
(9) |
Aug
(53) |
Sep
(26) |
Oct
(23) |
Nov
(32) |
Dec
(19) |
| 2009 |
Jan
(47) |
Feb
(49) |
Mar
(39) |
Apr
(61) |
May
(28) |
Jun
(19) |
Jul
(12) |
Aug
(10) |
Sep
(31) |
Oct
(16) |
Nov
(60) |
Dec
(26) |
| 2010 |
Jan
(17) |
Feb
(9) |
Mar
(32) |
Apr
(11) |
May
(24) |
Jun
(33) |
Jul
(5) |
Aug
(2) |
Sep
(7) |
Oct
(8) |
Nov
(17) |
Dec
(7) |
| 2011 |
Jan
(12) |
Feb
(16) |
Mar
(2) |
Apr
(12) |
May
(5) |
Jun
(10) |
Jul
(3) |
Aug
(3) |
Sep
(2) |
Oct
(1) |
Nov
(17) |
Dec
(1) |
| 2012 |
Jan
(9) |
Feb
(9) |
Mar
(8) |
Apr
(4) |
May
(2) |
Jun
(1) |
Jul
(4) |
Aug
(8) |
Sep
(11) |
Oct
(1) |
Nov
(2) |
Dec
(2) |
| 2013 |
Jan
|
Feb
(7) |
Mar
(4) |
Apr
(10) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
(3) |
| 2016 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|
From: coLinux a. <col...@he...> - 2009-08-31 14:33:33
|
The autobuild system has detected a new revision in the source repository. Review last changed from changelog.txt, also attached in mail. Download the compiled version: http://www.henrynestler.com/colinux/autobuild/devel-20090830/ colinux-0.8.0-20090830.src.tgz (683622 Bytes) daemons-0.8.0-20090830.dbg.zip (590615 Bytes) daemons-0.8.0-20090830.zip (477621 Bytes) Note, the autobuild compilation does not include an installer. Remember to reload the driver with these commands: colinux-daemon.exe --remove-driver colinux-daemon.exe --install-driver The vmlinux and modules are up to date. Please use last version from http://www.henrynestler.com/colinux/autobuild/devel-20090525/ The autobuild compilations are not official releases of Cooperative Linux software. There is no warranty that any autobuild version is stable. If use this autobuild version, please give us feedback of your experience. Job runs on machine with 64 bit version of gcc 4.1.2. A service from http://gcc.gnu.org/wiki/CompileFarm -- Lots of fun with newest version, Henry Nestler ------------------------------------------------------------------------ r1259 | henryn | 2009-08-30 20:39:13 +0000 (Sun, 30 Aug 2009) | 1 line Changed paths: M /branches/devel/NEWS M /branches/devel/configure * Bug#2847393: Configure detected wrong program versions. (Fixed by Steven Chen) ------------------------------------------------------------------------ |
|
From: SourceForge.net <no...@so...> - 2009-08-30 20:41:42
|
Bugs item #2847393, was opened at 2009-08-30 21:11 Message generated for change (Settings changed) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2847393&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Configuration Group: v0.8.x (devel) >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Steven Chen (megakilo) Assigned to: Nobody/Anonymous (nobody) Summary: build configure file bug Initial Comment: I used to build colinux on Debian. It works fine until recently I am building colinux on Fedora 11/CentOS 5.3. The configure test couldn't pass. Because the test for binutil reports a wrong version number. The "as --version" outputs "GNU assembler version 2.19.51.0.14-1.fc11 20090722". So the configure matched 1.0.14 (Checking as binutils for kernel ... (1.0.14) wrong version). I fix the configure by changing the wildchar ".*" to non-number "[^0-9]*". And the patch is attached. ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-08-30 22:41 Message: Thanks. Committed to SVN as revision 1259. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2847393&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-08-30 19:11:40
|
Bugs item #2847393, was opened at 2009-08-30 14:11 Message generated for change (Tracker Item Submitted) made by megakilo You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2847393&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Configuration Group: v0.8.x (devel) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Steven Chen (megakilo) Assigned to: Nobody/Anonymous (nobody) Summary: build configure file bug Initial Comment: I used to build colinux on Debian. It works fine until recently I am building colinux on Fedora 11/CentOS 5.3. The configure test couldn't pass. Because the test for binutil reports a wrong version number. The "as --version" outputs "GNU assembler version 2.19.51.0.14-1.fc11 20090722". So the configure matched 1.0.14 (Checking as binutils for kernel ... (1.0.14) wrong version). I fix the configure by changing the wildchar ".*" to non-number "[^0-9]*". And the patch is attached. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2847393&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-08-05 22:09:04
|
Feature Requests item #2832869, was opened at 2009-08-05 15:07 Message generated for change (Comment added) made by jpsalsman You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=2832869&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open >Priority: 6 Private: No Submitted By: James Salsman (jpsalsman) Assigned to: Nobody/Anonymous (nobody) Summary: Android Initial Comment: There's now a running "LiveAndroid" i386 distro ( http://code.google.com/p/live-android/ ) which should work. However, I am confused as to whether it is amenable to the Slackware HOWTO at http://article.gmane.org/gmane.linux.colinux.devel/1061/ or earlier, so I asked on the developer list for someone to expand http://colinux.wikia.com/index.php?title=Converting_Distributions#Android -- so far that says: Probably you will want VNC -- http://code.google.com/p/android-vnc-viewer/ -- but maybe X will work -- http://imandroid.org/2009/02/25/run-x-windows-within-android-via-x11-hack/ ---------------------------------------------------------------------- >Comment By: James Salsman (jpsalsman) Date: 2009-08-05 15:09 Message: I offer USD $100 to the first person to post a screen shot with instructions, and am boldly claiming priority 6. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=2832869&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-08-05 22:07:38
|
Feature Requests item #2832869, was opened at 2009-08-05 15:07 Message generated for change (Tracker Item Submitted) made by jpsalsman You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=2832869&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Private: No Submitted By: James Salsman (jpsalsman) Assigned to: Nobody/Anonymous (nobody) Summary: Android Initial Comment: There's now a running "LiveAndroid" i386 distro ( http://code.google.com/p/live-android/ ) which should work. However, I am confused as to whether it is amenable to the Slackware HOWTO at http://article.gmane.org/gmane.linux.colinux.devel/1061/ or earlier, so I asked on the developer list for someone to expand http://colinux.wikia.com/index.php?title=Converting_Distributions#Android -- so far that says: Probably you will want VNC -- http://code.google.com/p/android-vnc-viewer/ -- but maybe X will work -- http://imandroid.org/2009/02/25/run-x-windows-within-android-via-x11-hack/ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=2832869&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-08-05 19:55:15
|
Feature Requests item #2025225, was opened at 2008-07-22 17:16 Message generated for change (Comment added) made by josath You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=2025225&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Support for Windows x64 Initial Comment: All the machines in our office are running either Vista x64 or Server 2008 x64 and thus I can't use coLinux on my desktop despite really wanting to. Obviously there are driver signing issues to work through. Requiring the user to self-sign is not necessarily a blocker, at least for us. ---------------------------------------------------------------------- Comment By: David Rorex (josath) Date: 2009-08-05 12:55 Message: The developers have enough on their plate already, x64 is important, but there's only so many devs. If you really need to run linux under 64bit windows, check on virtualbox or vmware, they both have free versions which support that. Not quite as fast as colinux, but since you seem to already have a high end machine, the speed bump shouldn't bother you too much. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-08-05 12:49 Message: Whats with no X64 development? M$FT is signaling that x64 is going to be very important now, and those of us with lots of ram (8GB for me) and the need to run Windows for intensive tasks (IE those most likely to have x64). I cannot run X86 and I want my Linux apps to. Out in the cold, I would help developing but I am just a lowly Mechanical Engineer and am mostly useless outside of java. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-11-27 15:06 Message: Have started a Dashboard for 64 bit in the Wiki: http://colinux.wikia.com/wiki/Dashboard_for_developing_a_64_bit_coLinux Developers wanted! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=2025225&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-08-05 19:49:35
|
Feature Requests item #2025225, was opened at 2008-07-23 00:16 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=2025225&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Support for Windows x64 Initial Comment: All the machines in our office are running either Vista x64 or Server 2008 x64 and thus I can't use coLinux on my desktop despite really wanting to. Obviously there are driver signing issues to work through. Requiring the user to self-sign is not necessarily a blocker, at least for us. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-08-05 19:49 Message: Whats with no X64 development? M$FT is signaling that x64 is going to be very important now, and those of us with lots of ram (8GB for me) and the need to run Windows for intensive tasks (IE those most likely to have x64). I cannot run X86 and I want my Linux apps to. Out in the cold, I would help developing but I am just a lowly Mechanical Engineer and am mostly useless outside of java. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-11-27 23:06 Message: Have started a Dashboard for 64 bit in the Wiki: http://colinux.wikia.com/wiki/Dashboard_for_developing_a_64_bit_coLinux Developers wanted! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622066&aid=2025225&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-08-01 15:19:15
|
Bugs item #2830278, was opened at 2009-07-31 12:00 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2830278&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Linux Kernel Group: v0.7.x (release) Status: Closed Resolution: Duplicate Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Incorrect chksum of tcp packets. Initial Comment: In these days I installed colinux 0.74 on my windowsXP host. Everythig is ok except a strange problem about networking. I use "ndis-bridge" to connect a debian guest in colinux with the outer world, but whenever i connect from my host XP to a http or ssh server in the guest debian, a Incorrect chksum apears and the connection can not establish. On the other hand, visiting internet websites in debian is ok, and PING debian from my host XP is also ok. This problem confused me for days, following is the tcpdump output in my guest debian: 19:42:05.746243 IP (tos 0x0, ttl 128, id 15734, offset 0, flags [DF], proto TCP (6), length 48) dudu.1598 > cl.www: S, cksum 0x4f9d (correct), 514034366:514034366(0) win 65535 <mss 1460,nop,nop,sackOK> 0x0000: 00d0 f801 0101 001b 3805 a9d4 0800 4500 ........8.....E. 0x0010: 0030 3d76 4000 8006 39bf c0a8 010b c0a8 .0=v@...9....... 0x0020: 0137 063e 0050 1ea3 8abe 0000 0000 7002 .7.>.P........p. 0x0030: ffff 4f9d 0000 0204 05b4 0101 0402 ..O........... 19:42:05.756243 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 48) cl.www > dudu.1598: S, cksum 0xa5bb (correct), 4231763652:4231763652(0) ack 514034367 win 5840 <mss 1460,nop,nop,sackOK> 0x0000: 001b 3805 a9d4 00d0 f801 0101 0800 4500 ..8...........E. 0x0010: 0030 0000 4000 4006 b735 c0a8 0137 c0a8 .0..@.@..5...7.. 0x0020: 010b 0050 063e fc3b 96c4 1ea3 8abf 7012 ...P.>.;......p. 0x0030: 16d0 a5bb 0000 0204 05b4 0101 0402 .............. 19:42:05.746243 IP (tos 0x0, ttl 128, id 15735, offset 0, flags [DF], proto TCP (6), length 40) dudu.1598 > cl.www: ., cksum 0x83ad (incorrect (-> 0xe94f), 1:1(0) ack 1 win 65535 0x0000: 00d0 f801 0101 001b 3805 a9d4 0800 4500 ........8.....E. 0x0010: 0028 3d77 4000 8006 39c6 c0a8 010b c0a8 .(=w@...9....... 0x0020: 0137 063e 0050 1ea3 8abf fc3b 96c5 5010 .7.>.P.....;..P. 0x0030: ffff 83ad 0000 ...... 19:42:05.756243 IP (tos 0x0, ttl 128, id 15737, offset 0, flags [DF], proto TCP (6), length 130) dudu.1598 > cl.www: P 1:91(90) ack 1 win 65535 0x0000: 00d0 f801 0101 001b 3805 a9d4 0800 4500 ........8.....E. 0x0010: 0082 3d79 4000 8006 396a c0a8 010b c0a8 ..=y@...9j...... 0x0020: 0137 063e 0050 1ea3 8abf fc3b 96c5 5018 .7.>.P.....;..P. 0x0030: ffff 8407 0000 4745 5420 2f20 4854 5450 ......GET./.HTTP 0x0040: 2f31 2e30 0d0a 5573 6572 2d41 6765 6e74 /1.0..User-Agent 0x0050: 3a20 5767 6574 2f31 2e31 312e 310d 0a41 :.Wget/1.11.1..A 19:42:08.666287 IP (tos 0x0, ttl 128, id 15761, offset 0, flags [DF], proto TCP (6), length 130) dudu.1598 > cl.www: P 1:91(90) ack 1 win 65535 0x0000: 00d0 f801 0101 001b 3805 a9d4 0800 4500 ........8.....E. 0x0010: 0082 3d91 4000 8006 3952 c0a8 010b c0a8 ..=.@...9R...... 0x0020: 0137 063e 0050 1ea3 8abf fc3b 96c5 5018 .7.>.P.....;..P. 0x0030: ffff 8407 0000 4745 5420 2f20 4854 5450 ......GET./.HTTP 0x0040: 2f31 2e30 0d0a 5573 6572 2d41 6765 6e74 /1.0..User-Agent 0x0050: 3a20 5767 6574 2f31 2e31 312e 310d 0a41 :.Wget/1.11.1..A 19:42:09.146294 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 48) cl.www > dudu.1598: S, cksum 0xa5bb (correct), 4231763652:4231763652(0) ack 514034367 win 5840 <mss 1460,nop,nop,sackOK> 0x0000: 001b 3805 a9d4 00d0 f801 0101 0800 4500 ..8...........E. 0x0010: 0030 0000 4000 4006 b735 c0a8 0137 c0a8 .0..@.@..5...7.. 0x0020: 010b 0050 063e fc3b 96c4 1ea3 8abf 7012 ...P.>.;......p. 0x0030: 16d0 a5bb 0000 0204 05b4 0101 0402 .............. 19:42:09.146294 IP (tos 0x0, ttl 128, id 15762, offset 0, flags [DF], proto TCP (6), length 40) dudu.1598 > cl.www: ., cksum 0x83ad (incorrect (-> 0xe8f5), 91:91(0) ack 1 win 65535 0x0000: 00d0 f801 0101 001b 3805 a9d4 0800 4500 ........8.....E. 0x0010: 0028 3d92 4000 8006 39ab c0a8 010b c0a8 .(=.@...9....... 0x0020: 0137 063e 0050 1ea3 8b19 fc3b 96c5 5010 .7.>.P.....;..P. 0x0030: ffff 83ad 0000 ...... 19:42:14.656377 IP (tos 0x0, ttl 128, id 15795, offset 0, flags [DF], proto TCP (6), length 130) dudu.1598 > cl.www: P 1:91(90) ack 1 win 65535 0x0000: 00d0 f801 0101 001b 3805 a9d4 0800 4500 ........8.....E. 0x0010: 0082 3db3 4000 8006 3930 c0a8 010b c0a8 ..=.@...90...... 0x0020: 0137 063e 0050 1ea3 8abf fc3b 96c5 5018 .7.>.P.....;..P. 0x0030: ffff 8407 0000 4745 5420 2f20 4854 5450 ......GET./.HTTP 0x0040: 2f31 2e30 0d0a 5573 6572 2d41 6765 6e74 /1.0..User-Agent 0x0050: 3a20 5767 6574 2f31 2e31 312e 310d 0a41 :.Wget/1.11.1..A 19:42:15.146385 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 48) cl.www > dudu.1598: S, cksum 0xa5bb (correct), 4231763652:4231763652(0) ack 514034367 win 5840 <mss 1460,nop,nop,sackOK> 0x0000: 001b 3805 a9d4 00d0 f801 0101 0800 4500 ..8...........E. 0x0010: 0030 0000 4000 4006 b735 c0a8 0137 c0a8 .0..@.@..5...7.. 0x0020: 010b 0050 063e fc3b 96c4 1ea3 8abf 7012 ...P.>.;......p. 0x0030: 16d0 a5bb 0000 0204 05b4 0101 0402 .............. 19:42:15.146385 IP (tos 0x0, ttl 128, id 15796, offset 0, flags [DF], proto TCP (6), length 40) dudu.1598 > cl.www: ., cksum 0x83ad (incorrect (-> 0xe8f5), 91:91(0) ack 1 win 65535 0x0000: 00d0 f801 0101 001b 3805 a9d4 0800 4500 ........8.....E. 0x0010: 0028 3db4 4000 8006 3989 c0a8 010b c0a8 .(=.@...9....... 0x0020: 0137 063e 0050 1ea3 8b19 fc3b 96c5 5010 .7.>.P.....;..P. 0x0030: ffff 83ad 0000 ...... 19:42:26.646558 IP (tos 0x0, ttl 128, id 15863, offset 0, flags [DF], proto TCP (6), length 130) dudu.1598 > cl.www: P 1:91(90) ack 1 win 65535 0x0000: 00d0 f801 0101 001b 3805 a9d4 0800 4500 ........8.....E. 0x0010: 0082 3df7 4000 8006 38ec c0a8 010b c0a8 ..=.@...8....... 0x0020: 0137 063e 0050 1ea3 8abf fc3b 96c5 5018 .7.>.P.....;..P. 0x0030: ffff 8407 0000 4745 5420 2f20 4854 5450 ......GET./.HTTP 0x0040: 2f31 2e30 0d0a 5573 6572 2d41 6765 6e74 /1.0..User-Agent 0x0050: 3a20 5767 6574 2f31 2e31 312e 310d 0a41 :.Wget/1.11.1..A 19:42:27.146566 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 48) cl.www > dudu.1598: S, cksum 0xa5bb (correct), 4231763652:4231763652(0) ack 514034367 win 5840 <mss 1460,nop,nop,sackOK> 0x0000: 001b 3805 a9d4 00d0 f801 0101 0800 4500 ..8...........E. 0x0010: 0030 0000 4000 4006 b735 c0a8 0137 c0a8 .0..@.@..5...7.. 0x0020: 010b 0050 063e fc3b 96c4 1ea3 8abf 7012 ...P.>.;......p. 0x0030: 16d0 a5bb 0000 0204 05b4 0101 0402 .............. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-08-01 15:19 Message: Is just works! Thanks a lot for your help. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-08-01 12:23 Message: Please see Bug# 2688891: To make it usable, go into network card "Hardware options" - "Extensions" - Properties: "Checksum" - and change the Value into "Disable". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2830278&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-08-01 12:27:07
|
Bugs item #2688891, was opened at 2009-03-16 18:36 Message generated for change (Settings changed) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2688891&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Daemons (Windows) Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) >Summary: pcap/ndis bridge can't connent to colinux|tcp checksum error Initial Comment: Hi, i've upgraded my really old colinux install to the lastest develoment snapshot (20090315 and 20090305 for modules and kernel). Trying to setup networking i've seen that using pcap-bridge or ndis-bridge doesn't let me to connect to the colinux machine: - if i try to do a ping from colinux to host machine all goes ok - if i try to do a ping from my host machine to colinux all goes ok - if i try to download something from the web server that resides on host machine or from internet trought colinux (using wget for example) all goes ok - if i try to connect to a netcat server or an openssh server that resieds on colinux from the host machine it doesn't do anything. - if i try to connect to a netcat server or an openssh server that resides on colinux from a machine in the lan all goes ok Doing more tests revealed that the problem is with TCP packets because i tried to set up a netcat udp server on port 53 and testing it trought nslookup shows that colinux machine recived the request. I get the same problem using ndis-bridge and using pcap-bridge: from kernel messages all seems to be ok! ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-03-26 14:50 Message: Try installing VirtualBox With IP Checksumming enabled on my Realtek adaptor, NDIS Bridging cannot ping each other but with Virtualbox installed and its networking component assigned - it seems that my NDIS Bridge works perfect with no errors.. Its been running my webserver fine for a month :P ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-03-26 11:48 Message: thank you! i hope to give a look this weekend ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-03-25 22:48 Message: Inside Linux kernel exist some options, for example NETIF_F_IP_CSUM and NETIF_F_HW_CSUM. Both are not set, so Linux kernel should calculate the checksum. But I think, it does not. As I see, it does not for TCP and UDP packets. If you grep for these macros you will see how other net-drivers forwards this checksum calculation to the hardware chip. For coLinux we need to add this calculation in conet Linux kernel driver. Some interesting comments will find in Linux kernel header near the macro NETIF_F_IP_CSUM. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-03-17 13:57 Message: Really thanks! But, just a question: where i could look to fix checksum calculation? into conet module or into ndis/pcap-bridge daemon? ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-03-16 21:17 Message: That should be simple. I have the same symptom on my Intel PCI-Express. My card is a "Realtek RTL8102E Family PCI-E Fast Ethernet NIC". I can not connect via ssh from Host to coLinux. tcpdump on coLinux or Wireshark on Windows let's see the problem: The card does not accept packets with checksum errors. To make it usable, go into network card "Hardware options" - "Extensions" - Properties: "Checksum" - and change the Value into "Disable". Here is an example session of ssh connect from host to coLinux (the failed case). tcpdump on coLinux: 20:44:36.847616 arp who-has 192.168.2.100 tell 192.168.2.104 20:44:36.847616 arp reply 192.168.2.100 is-at 00:21:85:56:fb:35 20:44:41.647688 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: TCP (6), length: 48) 192.168.2.104.22 > 192.168.2.100.1057: S, cksum 0xabbc (correct), 1094183181:1094183181(0) ack 309852530 win 5840 20:44:41.657689 IP (tos 0x0, ttl 128, id 434, offset 0, flags [DF], proto: TCP (6), length: 40) 192.168.2.100.1057 > 192.168.2.104.22: ., cksum 0x8637 (incorrect (-> 0xef50), ack 1 win 65535 20:44:53.647869 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: TCP (6), length: 48) 192.168.2.104.22 > 192.168.2.100.1057: S, cksum 0xabbc (correct), 1094183181:1094183181(0) ack 309852530 win 5840 20:44:53.647869 IP (tos 0x0, ttl 128, id 435, offset 0, flags [DF], proto: TCP (6), length: 40) 192.168.2.100.1057 > 192.168.2.104.22: ., cksum 0x8637 (incorrect (-> 0xef50), ack 1 win 65535 The same output with Wireshark on Windows: 6 5.016498 00:ff:99:88:b0:00 00:21:85:56:fb:35 ARP Who has 192.168.2.100? Tell 192.168.2.104 7 5.016521 00:21:85:56:fb:35 00:ff:99:88:b0:00 ARP 192.168.2.100 is at 00:21:85:56:fb:35 8 9.829057 192.168.2.104 192.168.2.100 TCP ssh > startron [SYN, ACK] Seq=0 Ack=1 Win=5840 Len=0 MSS=1460 9 9.829114 192.168.2.100 192.168.2.104 TCP [TCP Dup ACK 3#2] startron > ssh [ACK] Seq=1 Ack=1 Win=65535 [TCP CHECKSUM INCORRECT] Len=0 10 21.814002 192.168.2.104 192.168.2.100 TCP ssh > startron [SYN, ACK] Seq=0 Ack=1 Win=5840 Len=0 MSS=1460 11 21.814062 192.168.2.100 192.168.2.104 TCP [TCP Dup ACK 3#3] startron > ssh [ACK] Seq=1 Ack=1 Win=65535 [TCP CHECKSUM INCORRECT] Len=0 I leave this bug opened, because it would be nicer to calculate the checksum before submit it into the windows network stack. Disable the receiver is a workaround. ---------------------------------------------------------------------- Comment By: daniele_dll (daniele_dll) Date: 2009-03-16 18:45 Message: Note: when i upgraded i've launched the necessary remove/install driver as requested in readme file ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2688891&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-08-01 12:23:40
|
Bugs item #2830278, was opened at 2009-07-31 14:00 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2830278&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Linux Kernel Group: v0.7.x (release) >Status: Closed >Resolution: Duplicate Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Incorrect chksum of tcp packets. Initial Comment: In these days I installed colinux 0.74 on my windowsXP host. Everythig is ok except a strange problem about networking. I use "ndis-bridge" to connect a debian guest in colinux with the outer world, but whenever i connect from my host XP to a http or ssh server in the guest debian, a Incorrect chksum apears and the connection can not establish. On the other hand, visiting internet websites in debian is ok, and PING debian from my host XP is also ok. This problem confused me for days, following is the tcpdump output in my guest debian: 19:42:05.746243 IP (tos 0x0, ttl 128, id 15734, offset 0, flags [DF], proto TCP (6), length 48) dudu.1598 > cl.www: S, cksum 0x4f9d (correct), 514034366:514034366(0) win 65535 <mss 1460,nop,nop,sackOK> 0x0000: 00d0 f801 0101 001b 3805 a9d4 0800 4500 ........8.....E. 0x0010: 0030 3d76 4000 8006 39bf c0a8 010b c0a8 .0=v@...9....... 0x0020: 0137 063e 0050 1ea3 8abe 0000 0000 7002 .7.>.P........p. 0x0030: ffff 4f9d 0000 0204 05b4 0101 0402 ..O........... 19:42:05.756243 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 48) cl.www > dudu.1598: S, cksum 0xa5bb (correct), 4231763652:4231763652(0) ack 514034367 win 5840 <mss 1460,nop,nop,sackOK> 0x0000: 001b 3805 a9d4 00d0 f801 0101 0800 4500 ..8...........E. 0x0010: 0030 0000 4000 4006 b735 c0a8 0137 c0a8 .0..@.@..5...7.. 0x0020: 010b 0050 063e fc3b 96c4 1ea3 8abf 7012 ...P.>.;......p. 0x0030: 16d0 a5bb 0000 0204 05b4 0101 0402 .............. 19:42:05.746243 IP (tos 0x0, ttl 128, id 15735, offset 0, flags [DF], proto TCP (6), length 40) dudu.1598 > cl.www: ., cksum 0x83ad (incorrect (-> 0xe94f), 1:1(0) ack 1 win 65535 0x0000: 00d0 f801 0101 001b 3805 a9d4 0800 4500 ........8.....E. 0x0010: 0028 3d77 4000 8006 39c6 c0a8 010b c0a8 .(=w@...9....... 0x0020: 0137 063e 0050 1ea3 8abf fc3b 96c5 5010 .7.>.P.....;..P. 0x0030: ffff 83ad 0000 ...... 19:42:05.756243 IP (tos 0x0, ttl 128, id 15737, offset 0, flags [DF], proto TCP (6), length 130) dudu.1598 > cl.www: P 1:91(90) ack 1 win 65535 0x0000: 00d0 f801 0101 001b 3805 a9d4 0800 4500 ........8.....E. 0x0010: 0082 3d79 4000 8006 396a c0a8 010b c0a8 ..=y@...9j...... 0x0020: 0137 063e 0050 1ea3 8abf fc3b 96c5 5018 .7.>.P.....;..P. 0x0030: ffff 8407 0000 4745 5420 2f20 4854 5450 ......GET./.HTTP 0x0040: 2f31 2e30 0d0a 5573 6572 2d41 6765 6e74 /1.0..User-Agent 0x0050: 3a20 5767 6574 2f31 2e31 312e 310d 0a41 :.Wget/1.11.1..A 19:42:08.666287 IP (tos 0x0, ttl 128, id 15761, offset 0, flags [DF], proto TCP (6), length 130) dudu.1598 > cl.www: P 1:91(90) ack 1 win 65535 0x0000: 00d0 f801 0101 001b 3805 a9d4 0800 4500 ........8.....E. 0x0010: 0082 3d91 4000 8006 3952 c0a8 010b c0a8 ..=.@...9R...... 0x0020: 0137 063e 0050 1ea3 8abf fc3b 96c5 5018 .7.>.P.....;..P. 0x0030: ffff 8407 0000 4745 5420 2f20 4854 5450 ......GET./.HTTP 0x0040: 2f31 2e30 0d0a 5573 6572 2d41 6765 6e74 /1.0..User-Agent 0x0050: 3a20 5767 6574 2f31 2e31 312e 310d 0a41 :.Wget/1.11.1..A 19:42:09.146294 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 48) cl.www > dudu.1598: S, cksum 0xa5bb (correct), 4231763652:4231763652(0) ack 514034367 win 5840 <mss 1460,nop,nop,sackOK> 0x0000: 001b 3805 a9d4 00d0 f801 0101 0800 4500 ..8...........E. 0x0010: 0030 0000 4000 4006 b735 c0a8 0137 c0a8 .0..@.@..5...7.. 0x0020: 010b 0050 063e fc3b 96c4 1ea3 8abf 7012 ...P.>.;......p. 0x0030: 16d0 a5bb 0000 0204 05b4 0101 0402 .............. 19:42:09.146294 IP (tos 0x0, ttl 128, id 15762, offset 0, flags [DF], proto TCP (6), length 40) dudu.1598 > cl.www: ., cksum 0x83ad (incorrect (-> 0xe8f5), 91:91(0) ack 1 win 65535 0x0000: 00d0 f801 0101 001b 3805 a9d4 0800 4500 ........8.....E. 0x0010: 0028 3d92 4000 8006 39ab c0a8 010b c0a8 .(=.@...9....... 0x0020: 0137 063e 0050 1ea3 8b19 fc3b 96c5 5010 .7.>.P.....;..P. 0x0030: ffff 83ad 0000 ...... 19:42:14.656377 IP (tos 0x0, ttl 128, id 15795, offset 0, flags [DF], proto TCP (6), length 130) dudu.1598 > cl.www: P 1:91(90) ack 1 win 65535 0x0000: 00d0 f801 0101 001b 3805 a9d4 0800 4500 ........8.....E. 0x0010: 0082 3db3 4000 8006 3930 c0a8 010b c0a8 ..=.@...90...... 0x0020: 0137 063e 0050 1ea3 8abf fc3b 96c5 5018 .7.>.P.....;..P. 0x0030: ffff 8407 0000 4745 5420 2f20 4854 5450 ......GET./.HTTP 0x0040: 2f31 2e30 0d0a 5573 6572 2d41 6765 6e74 /1.0..User-Agent 0x0050: 3a20 5767 6574 2f31 2e31 312e 310d 0a41 :.Wget/1.11.1..A 19:42:15.146385 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 48) cl.www > dudu.1598: S, cksum 0xa5bb (correct), 4231763652:4231763652(0) ack 514034367 win 5840 <mss 1460,nop,nop,sackOK> 0x0000: 001b 3805 a9d4 00d0 f801 0101 0800 4500 ..8...........E. 0x0010: 0030 0000 4000 4006 b735 c0a8 0137 c0a8 .0..@.@..5...7.. 0x0020: 010b 0050 063e fc3b 96c4 1ea3 8abf 7012 ...P.>.;......p. 0x0030: 16d0 a5bb 0000 0204 05b4 0101 0402 .............. 19:42:15.146385 IP (tos 0x0, ttl 128, id 15796, offset 0, flags [DF], proto TCP (6), length 40) dudu.1598 > cl.www: ., cksum 0x83ad (incorrect (-> 0xe8f5), 91:91(0) ack 1 win 65535 0x0000: 00d0 f801 0101 001b 3805 a9d4 0800 4500 ........8.....E. 0x0010: 0028 3db4 4000 8006 3989 c0a8 010b c0a8 .(=.@...9....... 0x0020: 0137 063e 0050 1ea3 8b19 fc3b 96c5 5010 .7.>.P.....;..P. 0x0030: ffff 83ad 0000 ...... 19:42:26.646558 IP (tos 0x0, ttl 128, id 15863, offset 0, flags [DF], proto TCP (6), length 130) dudu.1598 > cl.www: P 1:91(90) ack 1 win 65535 0x0000: 00d0 f801 0101 001b 3805 a9d4 0800 4500 ........8.....E. 0x0010: 0082 3df7 4000 8006 38ec c0a8 010b c0a8 ..=.@...8....... 0x0020: 0137 063e 0050 1ea3 8abf fc3b 96c5 5018 .7.>.P.....;..P. 0x0030: ffff 8407 0000 4745 5420 2f20 4854 5450 ......GET./.HTTP 0x0040: 2f31 2e30 0d0a 5573 6572 2d41 6765 6e74 /1.0..User-Agent 0x0050: 3a20 5767 6574 2f31 2e31 312e 310d 0a41 :.Wget/1.11.1..A 19:42:27.146566 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 48) cl.www > dudu.1598: S, cksum 0xa5bb (correct), 4231763652:4231763652(0) ack 514034367 win 5840 <mss 1460,nop,nop,sackOK> 0x0000: 001b 3805 a9d4 00d0 f801 0101 0800 4500 ..8...........E. 0x0010: 0030 0000 4000 4006 b735 c0a8 0137 c0a8 .0..@.@..5...7.. 0x0020: 010b 0050 063e fc3b 96c4 1ea3 8abf 7012 ...P.>.;......p. 0x0030: 16d0 a5bb 0000 0204 05b4 0101 0402 .............. ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-08-01 14:23 Message: Please see Bug# 2688891: To make it usable, go into network card "Hardware options" - "Extensions" - Properties: "Checksum" - and change the Value into "Disable". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2830278&group_id=98788 |
|
From: James S. <jsa...@gm...> - 2009-07-31 22:47:04
|
Well, I suppose I should have used Google Translate before posting here, but I still could sure use some help from someone who's done this before: http://code.google.com/p/live-android/ Both the http://colinux.wikia.com/wiki/Converting_Distributions instructions and the Slackware HOWTO I linked from http://colinux.wikia.com/wiki/Converting_Distributions#Android talk about doing things I haven't done and I don't know where to begin. I tweeted the Google Android guys, so they should at least be watching the wiki. Let them and/or them me if someone wants to do this on more than just a volunteer basis. Thanks in advance. Cheers, James Salsman ---------- Forwarded message ---------- From: James Salsman <jsa...@gm...> Date: Fri, Jul 31, 2009 at 3:27 PM Subject: help with German for Android i386 distro? To: col...@li... Does anyone on this list read German? Please see http://www.aptgetupdate.de/2009/07/07/android-live-i386/ Will Android work on coLinux? I could really use it to help debugging. I just started http://colinux.wikia.com/wiki/Converting_Distributions#Android as a stub section in case anyone figures it out. Please answer there if possible. If this is something that could be sponsored to make happen faster, please let me know and/or send a tweet to @cdibona and @jbqueru on Twitter to let the Google Android guys know. Thanks! Cheers, James Salsman |
|
From: James S. <jsa...@gm...> - 2009-07-31 22:27:36
|
Does anyone on this list read German? Please see http://www.aptgetupdate.de/2009/07/07/android-live-i386/ Will Android work on coLinux? I could really use it to help debugging. I just started http://colinux.wikia.com/wiki/Converting_Distributions#Androidas a stub section in case anyone figures it out. Please answer there if possible. If this is something that could be sponsored to make happen faster, please let me know and/or send a tweet to @cdibona and @jbqueru on Twitter to let the Google Android guys know. Thanks! Cheers, James Salsman |
|
From: SourceForge.net <no...@so...> - 2009-07-31 12:00:33
|
Bugs item #2830278, was opened at 2009-07-31 12:00 Message generated for change (Tracker Item Submitted) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2830278&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Linux Kernel Group: v0.7.x (release) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Incorrect chksum of tcp packets. Initial Comment: In these days I installed colinux 0.74 on my windowsXP host. Everythig is ok except a strange problem about networking. I use "ndis-bridge" to connect a debian guest in colinux with the outer world, but whenever i connect from my host XP to a http or ssh server in the guest debian, a Incorrect chksum apears and the connection can not establish. On the other hand, visiting internet websites in debian is ok, and PING debian from my host XP is also ok. This problem confused me for days, following is the tcpdump output in my guest debian: 19:42:05.746243 IP (tos 0x0, ttl 128, id 15734, offset 0, flags [DF], proto TCP (6), length 48) dudu.1598 > cl.www: S, cksum 0x4f9d (correct), 514034366:514034366(0) win 65535 <mss 1460,nop,nop,sackOK> 0x0000: 00d0 f801 0101 001b 3805 a9d4 0800 4500 ........8.....E. 0x0010: 0030 3d76 4000 8006 39bf c0a8 010b c0a8 .0=v@...9....... 0x0020: 0137 063e 0050 1ea3 8abe 0000 0000 7002 .7.>.P........p. 0x0030: ffff 4f9d 0000 0204 05b4 0101 0402 ..O........... 19:42:05.756243 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 48) cl.www > dudu.1598: S, cksum 0xa5bb (correct), 4231763652:4231763652(0) ack 514034367 win 5840 <mss 1460,nop,nop,sackOK> 0x0000: 001b 3805 a9d4 00d0 f801 0101 0800 4500 ..8...........E. 0x0010: 0030 0000 4000 4006 b735 c0a8 0137 c0a8 .0..@.@..5...7.. 0x0020: 010b 0050 063e fc3b 96c4 1ea3 8abf 7012 ...P.>.;......p. 0x0030: 16d0 a5bb 0000 0204 05b4 0101 0402 .............. 19:42:05.746243 IP (tos 0x0, ttl 128, id 15735, offset 0, flags [DF], proto TCP (6), length 40) dudu.1598 > cl.www: ., cksum 0x83ad (incorrect (-> 0xe94f), 1:1(0) ack 1 win 65535 0x0000: 00d0 f801 0101 001b 3805 a9d4 0800 4500 ........8.....E. 0x0010: 0028 3d77 4000 8006 39c6 c0a8 010b c0a8 .(=w@...9....... 0x0020: 0137 063e 0050 1ea3 8abf fc3b 96c5 5010 .7.>.P.....;..P. 0x0030: ffff 83ad 0000 ...... 19:42:05.756243 IP (tos 0x0, ttl 128, id 15737, offset 0, flags [DF], proto TCP (6), length 130) dudu.1598 > cl.www: P 1:91(90) ack 1 win 65535 0x0000: 00d0 f801 0101 001b 3805 a9d4 0800 4500 ........8.....E. 0x0010: 0082 3d79 4000 8006 396a c0a8 010b c0a8 ..=y@...9j...... 0x0020: 0137 063e 0050 1ea3 8abf fc3b 96c5 5018 .7.>.P.....;..P. 0x0030: ffff 8407 0000 4745 5420 2f20 4854 5450 ......GET./.HTTP 0x0040: 2f31 2e30 0d0a 5573 6572 2d41 6765 6e74 /1.0..User-Agent 0x0050: 3a20 5767 6574 2f31 2e31 312e 310d 0a41 :.Wget/1.11.1..A 19:42:08.666287 IP (tos 0x0, ttl 128, id 15761, offset 0, flags [DF], proto TCP (6), length 130) dudu.1598 > cl.www: P 1:91(90) ack 1 win 65535 0x0000: 00d0 f801 0101 001b 3805 a9d4 0800 4500 ........8.....E. 0x0010: 0082 3d91 4000 8006 3952 c0a8 010b c0a8 ..=.@...9R...... 0x0020: 0137 063e 0050 1ea3 8abf fc3b 96c5 5018 .7.>.P.....;..P. 0x0030: ffff 8407 0000 4745 5420 2f20 4854 5450 ......GET./.HTTP 0x0040: 2f31 2e30 0d0a 5573 6572 2d41 6765 6e74 /1.0..User-Agent 0x0050: 3a20 5767 6574 2f31 2e31 312e 310d 0a41 :.Wget/1.11.1..A 19:42:09.146294 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 48) cl.www > dudu.1598: S, cksum 0xa5bb (correct), 4231763652:4231763652(0) ack 514034367 win 5840 <mss 1460,nop,nop,sackOK> 0x0000: 001b 3805 a9d4 00d0 f801 0101 0800 4500 ..8...........E. 0x0010: 0030 0000 4000 4006 b735 c0a8 0137 c0a8 .0..@.@..5...7.. 0x0020: 010b 0050 063e fc3b 96c4 1ea3 8abf 7012 ...P.>.;......p. 0x0030: 16d0 a5bb 0000 0204 05b4 0101 0402 .............. 19:42:09.146294 IP (tos 0x0, ttl 128, id 15762, offset 0, flags [DF], proto TCP (6), length 40) dudu.1598 > cl.www: ., cksum 0x83ad (incorrect (-> 0xe8f5), 91:91(0) ack 1 win 65535 0x0000: 00d0 f801 0101 001b 3805 a9d4 0800 4500 ........8.....E. 0x0010: 0028 3d92 4000 8006 39ab c0a8 010b c0a8 .(=.@...9....... 0x0020: 0137 063e 0050 1ea3 8b19 fc3b 96c5 5010 .7.>.P.....;..P. 0x0030: ffff 83ad 0000 ...... 19:42:14.656377 IP (tos 0x0, ttl 128, id 15795, offset 0, flags [DF], proto TCP (6), length 130) dudu.1598 > cl.www: P 1:91(90) ack 1 win 65535 0x0000: 00d0 f801 0101 001b 3805 a9d4 0800 4500 ........8.....E. 0x0010: 0082 3db3 4000 8006 3930 c0a8 010b c0a8 ..=.@...90...... 0x0020: 0137 063e 0050 1ea3 8abf fc3b 96c5 5018 .7.>.P.....;..P. 0x0030: ffff 8407 0000 4745 5420 2f20 4854 5450 ......GET./.HTTP 0x0040: 2f31 2e30 0d0a 5573 6572 2d41 6765 6e74 /1.0..User-Agent 0x0050: 3a20 5767 6574 2f31 2e31 312e 310d 0a41 :.Wget/1.11.1..A 19:42:15.146385 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 48) cl.www > dudu.1598: S, cksum 0xa5bb (correct), 4231763652:4231763652(0) ack 514034367 win 5840 <mss 1460,nop,nop,sackOK> 0x0000: 001b 3805 a9d4 00d0 f801 0101 0800 4500 ..8...........E. 0x0010: 0030 0000 4000 4006 b735 c0a8 0137 c0a8 .0..@.@..5...7.. 0x0020: 010b 0050 063e fc3b 96c4 1ea3 8abf 7012 ...P.>.;......p. 0x0030: 16d0 a5bb 0000 0204 05b4 0101 0402 .............. 19:42:15.146385 IP (tos 0x0, ttl 128, id 15796, offset 0, flags [DF], proto TCP (6), length 40) dudu.1598 > cl.www: ., cksum 0x83ad (incorrect (-> 0xe8f5), 91:91(0) ack 1 win 65535 0x0000: 00d0 f801 0101 001b 3805 a9d4 0800 4500 ........8.....E. 0x0010: 0028 3db4 4000 8006 3989 c0a8 010b c0a8 .(=.@...9....... 0x0020: 0137 063e 0050 1ea3 8b19 fc3b 96c5 5010 .7.>.P.....;..P. 0x0030: ffff 83ad 0000 ...... 19:42:26.646558 IP (tos 0x0, ttl 128, id 15863, offset 0, flags [DF], proto TCP (6), length 130) dudu.1598 > cl.www: P 1:91(90) ack 1 win 65535 0x0000: 00d0 f801 0101 001b 3805 a9d4 0800 4500 ........8.....E. 0x0010: 0082 3df7 4000 8006 38ec c0a8 010b c0a8 ..=.@...8....... 0x0020: 0137 063e 0050 1ea3 8abf fc3b 96c5 5018 .7.>.P.....;..P. 0x0030: ffff 8407 0000 4745 5420 2f20 4854 5450 ......GET./.HTTP 0x0040: 2f31 2e30 0d0a 5573 6572 2d41 6765 6e74 /1.0..User-Agent 0x0050: 3a20 5767 6574 2f31 2e31 312e 310d 0a41 :.Wget/1.11.1..A 19:42:27.146566 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 48) cl.www > dudu.1598: S, cksum 0xa5bb (correct), 4231763652:4231763652(0) ack 514034367 win 5840 <mss 1460,nop,nop,sackOK> 0x0000: 001b 3805 a9d4 00d0 f801 0101 0800 4500 ..8...........E. 0x0010: 0030 0000 4000 4006 b735 c0a8 0137 c0a8 .0..@.@..5...7.. 0x0020: 010b 0050 063e fc3b 96c4 1ea3 8abf 7012 ...P.>.;......p. 0x0030: 16d0 a5bb 0000 0204 05b4 0101 0402 .............. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2830278&group_id=98788 |
|
From: H. N. <hen...@ar...> - 2009-07-13 18:32:36
|
Hello, it's not only the signing problem. 64 bit driver is not supported by source. Of curse, you can run 32 bit application under 64 bit, but all drivers must handle 64 bit. For coLinux we must complete save and restore all register between the Operating System switch, and that is currently not written. More you will find in the wiki http://colinux.wikia.com/wiki/Dashboard_for_developing_a_64_bit_coLinux Henry Michael McStarfighter wrote: > coLinux is using kernel drivers and so it can't run under the WoW64 mode. A > 64-bit version of colinux would be very cool but AFAIK there is no version > atm because of the damn f... "signed driver" situation. I don't understand > why this isn't a case at a court... > > 2009/7/13 Ole Loots > > > Hi there, > > > > I was just trying to install coLinux 0.7.4 on a Vista 64Bit Pc... but > > sadly the installer aborts because of 64 Bit :( ! > > > > So i was a little bit frustrated,.. why can't I force the installation? > > > > I'm using ReadyDriverPlus to run unsigned Drivers with Vista 64Bit... so > > that shouldn't be the problem! > > > > Afaik, all non 64Bit software runs in 32bit emulation mode on x64 CPU's, > > is there an option to force installation on 64bit systems? Could someone > > provide such an installer? I want to give it a try! :) > > > > Have a nice day, > > > > Ole -- --------------------------------------------------------- ... Es folgt Arcor Werbung | Ads follows by Arcor ... Jetzt neu: Arcor- Online Butler 5.0 als kostenfreier Download! Der Arcor-Online Butler loggt Sie automatisch in unsere Online-Dienste ein und Sie kommen mit einem Klick zu Ihren E-Mails, zum Chat und vielem mehr. www.arcor.de/rd/butler |
|
From: Michael M. <mcs...@gm...> - 2009-07-13 09:45:13
|
coLinux is using kernel drivers and so it can't run under the WoW64 mode. A 64-bit version of colinux would be very cool but AFAIK there is no version atm because of the damn f... "signed driver" situation. I don't understand why this isn't a case at a court... 2009/7/13 Ole Loots <ol...@mo...> > Hi there, > > I was just trying to install coLinux 0.7.4 on a Vista 64Bit Pc... but > sadly the installer aborts because of 64 Bit :( ! > > So i was a little bit frustrated,.. why can't I force the installation? > > I'm using ReadyDriverPlus to run unsigned Drivers with Vista 64Bit... so > that shouldn't be the problem! > > Afaik, all non 64Bit software runs in 32bit emulation mode on x64 CPU's, > is there an option to force installation on 64bit systems? Could someone > provide such an installer? I want to give it a try! :) > > Have a nice day, > > Ole > > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
|
From: Ole L. <ol...@mo...> - 2009-07-13 09:24:26
|
Hi there, I was just trying to install coLinux 0.7.4 on a Vista 64Bit Pc... but sadly the installer aborts because of 64 Bit :( ! So i was a little bit frustrated,.. why can't I force the installation? I'm using ReadyDriverPlus to run unsigned Drivers with Vista 64Bit... so that shouldn't be the problem! Afaik, all non 64Bit software runs in 32bit emulation mode on x64 CPU's, is there an option to force installation on 64bit systems? Could someone provide such an installer? I want to give it a try! :) Have a nice day, Ole |
|
From: SourceForge.net <no...@so...> - 2009-07-03 17:28:17
|
Bugs item #2815128, was opened at 2009-07-01 13:11 Message generated for change (Settings changed) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2815128&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Crash / BSOD Group: v0.7.x (release) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) >Summary: BSOD during install or uninstall on Windows Server 2003 Initial Comment: Whenever I try running the colinux 0.7.4 installer I receive a Blue Screen of Death, It says irql_not_less_or_equal. At first I thought that the problem might be with one of the components. So I unchecked all the components during the installer, but I still get the BSOD. The operating system I am running is Windows Server 2003 Enterprise. Any Idea what the problem might be? ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-07-03 19:27 Message: Steve has send me the minidump. He was trying uninstalling coLinux 0.7.4 I added the symbols for linux.sys. The result have attached. STACK_TEXT: b5c888e4 nt+0x8c993 b5c88998 nt+0x2998b b5c889c8 linux!co_os_mutex_acquire+0x18 (linux+0xc8b8) b5c889f8 linux!co_manager_open+0x8F (linux+0x1e6f) b5c88a48 linux!dispatch_wrapper@8+0x2D7 (linux+0x7c37) ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-07-02 23:04 Message: Steve, please attach the minidump file to an email and send it to my SF account (henryn). ---------------------------------------------------------------------- Comment By: Steven Barendregt (stevebarendregt) Date: 2009-07-02 02:40 Message: yes it is 32-bit windows. Unfortunately When I try to uninstall Colinux, I get the BSOD again. I have recorded the minidump of this BSOD, but i can't figure out how to attach the file here. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-07-01 23:01 Message: I hope: This is a 32 bit Windows? Try a clean uninstall, than reboot Windows and install the driver manually from this location: http://www.henrynestler.com/colinux/releases/0.7.4/packages/ BSOD is better, than simple reboot. We need the stack backtrace. Please try to enable a "minidump", than lets crash again and analyze the minidump with WinDbg.exe, follow steps "Howto use Windows crash dump" from file "debugging.txt": http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/doc/debugging ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2815128&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-07-03 17:27:08
|
Bugs item #2815128, was opened at 2009-07-01 13:11 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2815128&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Crash / BSOD Group: v0.7.x (release) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: BSOD during install Initial Comment: Whenever I try running the colinux 0.7.4 installer I receive a Blue Screen of Death, It says irql_not_less_or_equal. At first I thought that the problem might be with one of the components. So I unchecked all the components during the installer, but I still get the BSOD. The operating system I am running is Windows Server 2003 Enterprise. Any Idea what the problem might be? ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-07-03 19:27 Message: Steve has send me the minidump. He was trying uninstalling coLinux 0.7.4 I added the symbols for linux.sys. The result have attached. STACK_TEXT: b5c888e4 nt+0x8c993 b5c88998 nt+0x2998b b5c889c8 linux!co_os_mutex_acquire+0x18 (linux+0xc8b8) b5c889f8 linux!co_manager_open+0x8F (linux+0x1e6f) b5c88a48 linux!dispatch_wrapper@8+0x2D7 (linux+0x7c37) ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-07-02 23:04 Message: Steve, please attach the minidump file to an email and send it to my SF account (henryn). ---------------------------------------------------------------------- Comment By: Steven Barendregt (stevebarendregt) Date: 2009-07-02 02:40 Message: yes it is 32-bit windows. Unfortunately When I try to uninstall Colinux, I get the BSOD again. I have recorded the minidump of this BSOD, but i can't figure out how to attach the file here. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-07-01 23:01 Message: I hope: This is a 32 bit Windows? Try a clean uninstall, than reboot Windows and install the driver manually from this location: http://www.henrynestler.com/colinux/releases/0.7.4/packages/ BSOD is better, than simple reboot. We need the stack backtrace. Please try to enable a "minidump", than lets crash again and analyze the minidump with WinDbg.exe, follow steps "Howto use Windows crash dump" from file "debugging.txt": http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/doc/debugging ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2815128&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-07-02 21:04:56
|
Bugs item #2815128, was opened at 2009-07-01 13:11 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2815128&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Crash / BSOD Group: v0.7.x (release) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: BSOD during install Initial Comment: Whenever I try running the colinux 0.7.4 installer I receive a Blue Screen of Death, It says irql_not_less_or_equal. At first I thought that the problem might be with one of the components. So I unchecked all the components during the installer, but I still get the BSOD. The operating system I am running is Windows Server 2003 Enterprise. Any Idea what the problem might be? ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-07-02 23:04 Message: Steve, please attach the minidump file to an email and send it to my SF account (henryn). ---------------------------------------------------------------------- Comment By: Steven Barendregt (stevebarendregt) Date: 2009-07-02 02:40 Message: yes it is 32-bit windows. Unfortunately When I try to uninstall Colinux, I get the BSOD again. I have recorded the minidump of this BSOD, but i can't figure out how to attach the file here. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-07-01 23:01 Message: I hope: This is a 32 bit Windows? Try a clean uninstall, than reboot Windows and install the driver manually from this location: http://www.henrynestler.com/colinux/releases/0.7.4/packages/ BSOD is better, than simple reboot. We need the stack backtrace. Please try to enable a "minidump", than lets crash again and analyze the minidump with WinDbg.exe, follow steps "Howto use Windows crash dump" from file "debugging.txt": http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/doc/debugging ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2815128&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-07-02 00:40:18
|
Bugs item #2815128, was opened at 2009-07-01 06:11 Message generated for change (Comment added) made by stevebarendregt You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2815128&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Crash / BSOD Group: v0.7.x (release) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: BSOD during install Initial Comment: Whenever I try running the colinux 0.7.4 installer I receive a Blue Screen of Death, It says irql_not_less_or_equal. At first I thought that the problem might be with one of the components. So I unchecked all the components during the installer, but I still get the BSOD. The operating system I am running is Windows Server 2003 Enterprise. Any Idea what the problem might be? ---------------------------------------------------------------------- Comment By: Steven Barendregt (stevebarendregt) Date: 2009-07-01 19:40 Message: yes it is 32-bit windows. Unfortunately When I try to uninstall Colinux, I get the BSOD again. I have recorded the minidump of this BSOD, but i can't figure out how to attach the file here. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-07-01 16:01 Message: I hope: This is a 32 bit Windows? Try a clean uninstall, than reboot Windows and install the driver manually from this location: http://www.henrynestler.com/colinux/releases/0.7.4/packages/ BSOD is better, than simple reboot. We need the stack backtrace. Please try to enable a "minidump", than lets crash again and analyze the minidump with WinDbg.exe, follow steps "Howto use Windows crash dump" from file "debugging.txt": http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/doc/debugging ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2815128&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-07-01 21:01:23
|
Bugs item #2815128, was opened at 2009-07-01 13:11 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2815128&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Crash / BSOD Group: v0.7.x (release) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: BSOD during install Initial Comment: Whenever I try running the colinux 0.7.4 installer I receive a Blue Screen of Death, It says irql_not_less_or_equal. At first I thought that the problem might be with one of the components. So I unchecked all the components during the installer, but I still get the BSOD. The operating system I am running is Windows Server 2003 Enterprise. Any Idea what the problem might be? ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-07-01 23:01 Message: I hope: This is a 32 bit Windows? Try a clean uninstall, than reboot Windows and install the driver manually from this location: http://www.henrynestler.com/colinux/releases/0.7.4/packages/ BSOD is better, than simple reboot. We need the stack backtrace. Please try to enable a "minidump", than lets crash again and analyze the minidump with WinDbg.exe, follow steps "Howto use Windows crash dump" from file "debugging.txt": http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/doc/debugging ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2815128&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-07-01 11:11:56
|
Bugs item #2815128, was opened at 2009-07-01 11:11 Message generated for change (Tracker Item Submitted) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2815128&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Crash / BSOD Group: v0.7.x (release) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: BSOD during install Initial Comment: Whenever I try running the colinux 0.7.4 installer I receive a Blue Screen of Death, It says irql_not_less_or_equal. At first I thought that the problem might be with one of the components. So I unchecked all the components during the installer, but I still get the BSOD. The operating system I am running is Windows Server 2003 Enterprise. Any Idea what the problem might be? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2815128&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-06-30 06:27:28
|
Bugs item #2798299, was opened at 2009-05-29 12:04 Message generated for change (Comment added) made by dpashev You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2798299&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Crash / BSOD Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Dimitar Pashev (dpashev) Assigned to: Nobody/Anonymous (nobody) Summary: System crashed afrer upgrade to 0.7.4 and SMP_WORKAROUND=Y Initial Comment: System crashed afrer upgrade from 0.7.3.0 to 0.7.4.0 and COLINUX_NO_SMP_WORKAROUND=Y OS Windows XP,2003 Error code is: 0x1000007f (0x00000008, 0xba338d70, 0x00000000, 0x00000000). A After downgrade to 0.7.3.0 system working OK ---------------------------------------------------------------------- >Comment By: Dimitar Pashev (dpashev) Date: 2009-06-30 09:26 Message: Processors Information ------------------------------------------------------------------------------------ Processor 1 (ID = 0) Number of cores 2 (max 2) Number of threads 2 (max 2) Name Intel Pentium D 820 Codename SmithField Specification Intel(R) Pentium(R) D CPU 2.80GHz Package Socket 775 LGA (platform ID = 4h) CPUID F.4.7 Extended CPUID F.4 Core Stepping B0 Technology 90 nm Core Speed 2800.2 MHz (14.0 x 200.0 MHz) Rated Bus speed 800.1 MHz Stock frequency 2800 MHz Instructions sets MMX, SSE, SSE2, SSE3, EM64T L1 Data cache 2 x 16 KBytes, 8-way set associative, 64-byte line size Trace cache 2 x 12 Kuops, 8-way set associative L2 cache 2 x 1024 KBytes, 8-way set associative, 64-byte line size FID/VID Control no Features XD ----- colinux /proc/cpuinfo ---- processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 4 model name : Intel(R) Pentium(R) D CPU 2.80GHz stepping : 7 cpu MHz : 2800.000 cache size : 1024 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni mon itor ds_cpl cid cx16 xtpr lahf_lm bogomips : 5688.52 clflush size : 64 ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-06-29 20:18 Message: And 20080907-Snapshot crashed, with same configuration? What is the CPU manufacturer (Intel or AMD)? What detected a Linux (better would be a native Linux or Knoppix) for this cpu in the flags? type: cat /proc/cpuinfo PS: 2008-08-23T14:15:00 r1118 is without sysenter support 2008-09-07T12:26:17 r1119 is the first build with sysenter ---------------------------------------------------------------------- Comment By: Dimitar Pashev (dpashev) Date: 2009-06-29 09:43 Message: with 20080823-Snapshot work - OK ! ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-06-27 16:22 Message: Dimitar, please say, works 0.7.4 without COLINUX_NO_SMP_WORKAROUND=Y ? Works an older snapsot? For example: http://www.henrynestler.com/colinux/testing/devel-0.8.0/ 20080823-Snapshot ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-06-03 10:14 Message: Previous is not entirely true. first time: "colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram" -> BOOT OK!!! second time: "colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram" -> CRASH !!! Blue screen BCCode : 1000007f BCP1 : 00000008 BCP2 : 80042000 BCP3 : 00000000 BCP4 : 00000000 OSVer : 5_1_2600 SP : 3_0 Product : 256_1 ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-06-03 09:48 Message: >Do you used the file "vmlinux", that was distributed with the installation >(or a self made kernel)? - distributed with the installation >Runs the quick test with initrd and the kernel from installation >directory >"colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0" ? BOOT OK !!!!! but, if remove root=/dev/ram0, windows crashed after few seconds !!! colinux-daemon kernel=vmlinux initrd=initrd.gz -> Crash after few seconds ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-06-03 00:49 Message: Hm, that's odd. When it's crashing? Some times after install (without starting colinux-daemon)? After executing the kernel (with or without boot messages)? Or on shutdown coLinux? Do you used the file "vmlinux", that was distributed with the installation (or a self made kernel)? Runs the quick test with initrd and the kernel from installation directory "colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0" ? Such crash is typically from the code in our passage page, because we don't have a trap handler there. The changes on passage page between 0.7.3 (SVN r1055) and 0.7.4 (SVN r1245) are minimal. Exactly it was only r1198, r1192 and r1119: http://colinux.svn.sourceforge.net/viewvc/colinux/branches/devel/src/colinux/arch/i386/passage.c?view=log&pathrev=1245 I afraid, it is the change on "sysenter" (X86_FEATURE_SEP). Add "nosep" to the kernel command line and try to boot. This will disable the SEP feature on Linux side. You can try some of the changes, step by step from snapshot archive: http://www.henrynestler.com/colinux/testing/devel-0.8.0/ 20080823-Snapshot : SVN revision r1118 without sysenter 20080907-Snapshot : SVN revision r1119 with sysenter PS: Please login on SF berore answer. So, we know, that is the same user from beginning. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-06-01 15:17 Message: Yes, dir linux.sys 15.04.2009 г. 21:59 84 992 linux.sys ------------------------------------------------------ C:\Program Files\coLinux>colinux-daemon.exe --remove-driver Cooperative Linux Daemon, 0.7.4 Daemon compiled on Wed Apr 15 18:59:08 2009 ------------------------------------------------------ C:\Program Files\coLinux>colinux-daemon.exe --install-driver Cooperative Linux Daemon, 0.7.4 Daemon compiled on Wed Apr 15 18:59:08 2009 loading C:\Program Files\coLinux\linux.sys daemon: driver installed ------------------------------------------------------ C:\Program Files\coLinux>colinux-daemon.exe --status-driver Cooperative Linux Daemon, 0.7.4 Daemon compiled on Wed Apr 15 18:59:08 2009 checking if the driver is installed current state: 4 (fully initialized) current number of monitors: 0 current linux api version: 12 current periphery api version: 22 Driver compiled on: Wed Apr 15 18:59:08 2009 ----------------------------------------------------------- ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 00000008, EXCEPTION_DOUBLE_FAULT Arg2: ba338d70 Arg3: 00000000 Arg4: 00000000 ----------------------------------------------------- MODULE_NAME: nt FAULTING_MODULE: 804d7000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 498c11d3 BUGCHECK_STR: 0x7f_8 DEFAULT_BUCKET_ID: DRIVER_FAULT LAST_CONTROL_TRANSFER: from 00000000 to 80543561 STACK_TEXT: STACK_COMMAND: kb FOLLOWUP_IP: nt!Kei386EoiHelper+16a5 80543561 ebee jmp nt!Kei386EoiHelper+0x1695 (80543551) SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!Kei386EoiHelper+16a5 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: ntkrpamp.exe BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner --------- ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2009-05-30 01:02 Message: Are you sure to have upgrade it right, and the driver was successfully replaced? Have you tried 1. execute "colinux-daemon --remove-driver" 2. execute "colinux-daemon --install-driver" Does it also crash without "COLINUX_NO_SMP_WORKAROUND=Y" ? Do you have a minidump and can you please analyze it? (see debugging.txt) ---------------------------------------------------------------------- Comment By: Dimitar Pashev (dpashev) Date: 2009-05-29 12:16 Message: http://msdn.microsoft.com/en-us/library/ms795478.aspx -------- Bug Check 0x7F: UNEXPECTED_KERNEL_MODE_TRAP Parameter: 0x00000008, or Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Typically, the two exceptions are handled serially. However, there are several exceptions that cannot be handled serially, and in this situation the processor signals a double fault. There are two common causes of a double fault: A kernel stack overflow. This overflow occurs when a guard page is hit, and the kernel tries to push a trap frame. Because there is no stack left, a stack overflow results, causing the double fault. If you think this overview has occurred, use the !thread debugger extension to determine the stack limits, and then use the kb (Display Stack Backtrace) debugger command with a large parameter (for example, kb 100) to display the full stack. A hardware problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2798299&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-06-29 20:08:29
|
Bugs item #1861876, was opened at 2008-01-02 00:57 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1861876&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 7 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: 20071203-Snapshot -- ifconfig reports no networking Initial Comment: I downloaded http://www.henrynestler.com/colinux/testing/devel-0.8.0/20071203-Snapshot/devel-coLinux-20071203.exe (and the source). When I tried to install devel-coLinux-20071203.exe on top of (in the same directory, saving a copy of my OLD vmlinux first) the prior snapshot (devel-coLinux-20070819.exe) it complained about API mismatches --- so I recompiled from source and built the installer.exe also. Now I can get coLinux to boot and login with everything working. You might want to look into making coLinux upgrades easier. If a TINY portion of the interface was written in assembly then the daemon could actually TEST if it can run instead of assuming that GCC 4.1 and GCC 4.2 are not compatable ... But that is my 'fancy' setup (bleeding edge compiler and (nearly) ALL xconfig options turned ON!). After overcomming those troubles that "BUG" is this: Where I am now is that I can run the installer that I compiled, or run devel-coLinux-20071203.exe and the networking is not correct. If I type "ifconfig" Linux seems to think that my only interface is "lo" -- I no longer have "eth0" ! If I ONLY execute "devel-coLinux-20070819.exe" (in WinXP), change NOTHING, like my config file, (except for the line "kernel=vmlinux-1" to swap API versions) or any scripts in the Linux and simply install "devel-coLinux-20070819.exe" on top of "devel-coLinux-20071203.exe" then my networking works fine. My networking has worked for years, only the newest "devel-coLinux-20071203.exe" has caused a loss of interfaces. Typing "/etc/init.d/networking restart" claims that the interfaces are gone. I can't cut and paste from the console but here is a bit of it: eth0: ERROR while getting interface flags: No such device SIOCSIFNETMASK: No such device SIOCSIFBRDADDR: No such device eth0: ERROR while getting interface flags: No such device eth0: ERROR while getting interface flags: No such device Failed to bring up eth0. (same for eth1 and eth2). Running from the DOS prompt ([START] 'run' "cmd") I get these sort of messages: C:\colinux>colinux-daemon.exe -v 10 @coLinux.conf -t fltk Cooperative Linux Daemon, 0.8.0 Compiled on Dec 3 2007 23:38:28 using 'vmlinux-29' as kernel image configuring 1024 MB of virtual RAM mapping cobd0 to \??\c:\coLinux\Debian-3.0r2.ext3-mit-backports.14gb mapping cobd1 to \??\c:\colinux\swap_1024Mb mapping cobd3 to \??\c:\colinux\drive_1.ext3.14GB mapping cobd4 to \??\c:\colinux\drive_2.ext3.14GB mapping cobd5 to \??\c:\coLinux\drive_spare.ext3.2GB configured TAP at '' device as eth0 MAC address: auto generated configured PCAP bridge at '' device as eth1 MAC address: auto generated configured Slirp as eth2 MAC address: auto generated mapping cofs1 to \??\E:\ mapping cofs0 to \??\c:\ using 'initrd.gz' as initrd image mapping cofs31 to \??\C:\colinux kernel boot parameters: 'root=/dev/cobd0 ro apic=debug lapic dvd=:cobd2 profile=2' creating monitor reading initrd from (initrd.gz) initrd size: 415873 bytes PID: 5736 colinux: launching console executing: colinux-console-fltk -a 5736 launching daemon for conet0 executing: colinux-net-daemon -i 5736 -u 0 launching daemon for conet1 executing: colinux-bridged-net-daemon -i 5736 -u 1 -mac 00:ff:99:e0:52:60 -p 1 launching daemon for conet2 executing: colinux-slirp-net-daemon -i 5736 -u 2 colinux: booting colinux-net-daemon: auto selecting TAP colinux-net-daemon: found TAP device named "Local Area Connection 3" colinux-net-daemon: opening TAP: "Local Area Connection 3" colinux-net-daemon: TAP driver version 8.4 colinux-net-daemon: enabling TAP... conet-slirp-daemon: running Linux version 2.6.22-co-0.8.0 (root@colinux) (gcc version 4.2.2 20070804 (prerelease)) #1 PREEMPT Tu e Jan 1 02:51:41 PST 2008 1000MB LOWMEM available. initrd enabled: start: 0xfe79a000 size: 0x00065881 .... (Here is something I have not seen previously) conet-bridged-daemon: Auto selecting name for bridged interface conet-bridged-daemon: adapter Adapter for generic dialup and VPN capture doesn't have a connection conet-bridged-daemon: checking connection: Local Area Connection conet-bridged-daemon: checking connection: Local Area Connection 2 conet-bridged-daemon: checking connection: Local Area Connection 3 conet-bridged-daemon: listening on: TAP-Win32 Adapter V8 (coLinux) (Microsoft's Packet Scheduler) ... conet-bridged-daemon: listening for: (ether dst 00:ff:99:e0:52:60) or (ether broadcast or multicast) or (ip broadcast or multicast) .... (more lines deleted) : Registered protocol family 10 lo: Disabled Privacy Extensions IPv6 over IPv4 tunneling driver sit0: Disabled Privacy Extensions ip_tables: (C) 2000-2006 Netfilter Core Team Netfilter messages via NETLINK v0.30. nf_conntrack version 0.5.0 (8000 buckets, 64000 max) .... (more lines deleted) It ends up that "ipconfig" finds "lo" (and "sit0" which I never did finish writing the configure script for -- but it is detected ;( ). It is "as if" the 'conet-bridged-daemon' will NOT properly read my 'network methods' in my coLinux.conf file. The end of my coLinux.conf is: eth0=tuntap eth1=pcap-bridge eth2=slirp So I have had no trouble with "devel-coLinux-20070819.exe" and earlier but can't use "devel-coLinux-20071203.exe" (as far as 'seeing' my network interfaces). Other than this one issue everything seems OK. Since I don't have networking I can't use X11 (and don't way to fiddle with the tiny console) so I am going back to the prior version. Rob ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-06-29 22:08 Message: To allow dual boot, you can bypass the rename only for coLinux by adding a line with DRIVER "conet" to the file net_persistent_names.rules some there in top of file where other skips exist: # ignore "conet" interfaces DRIVERS=="conet" GOTO="persistent_net_generator_end" This also fixes the problem on changing between different coLinux version (0.7.3 and newer) and the problem between starts from command line and as service (different Windows user). For Debian 4.0 insert the '+' marked lines into file /etc/udev/rules.d/z45_persistent-net-generator.rules near line 15: ` # ignore "secondary" raw interfaces of the madwifi driver KERNEL=="ath*", ATTRS{type}=="802", GOTO="persistent_net_generator_end" + +# ignore "conet" interfaces +DRIVERS=="conet", GOTO="persistent_net_generator_end" + # provide nice comments for the generated rules SUBSYSTEMS=="pci", \ ENV{COMMENT}="PCI device $attr{vendor}:$attr{device}" ` For Ubuntu 8.1 insert '+' marked lines into file /etc/udev/rules.d/75-persistent-net-generator.rules at line 26: ` # ignore Xen virtual interfaces SUBSYSTEMS=="xen", GOTO="persistent_net_generator_end" + +# Do not rename coLinux network devices +DRIVERS=="conet", GOTO="persistent_net_generator_end" + # read MAC address ENV{MATCHADDR}="$attr{address}" ` ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-02-28 22:58 Message: Logged In: YES user_id=579204 Originator: NO If a user change colinux version from 0.7.x to 0.8.0, any time must remove the lines in "/etc/udev/rules.d/z25_persistent-net.rules" That means if you starts 0.8.x, than 0.7.x and 0.8.x later, than the promlems comes again. If you switching more often between coLinux version 0.7.x and 0.8.x, should set a MAC in your colinux.conf, or yust kill the file on every startup by adding such line into the network startup script (near /etc/initd.d/network...): echo "#dummy" > /etc/udev/rules.d/z25_persistent-net.rules ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-01-13 00:55 Message: Logged In: YES user_id=579204 Originator: NO http://www.colinux.org/snapshots/ build 20080112 saves automatic generated MAC address into windows registry now. Please test it and report usability. Thanks. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-01-06 19:27 Message: Logged In: YES user_id=579204 Originator: NO I'm sorry for the pain with eth counts, and thanks for reporting. I'm think about saving the random numbers after the first creation somethere in registry. The name for pcap-bridge should never be empty! In some cases the pcap-bridge would detect the TAP-Win32 as outgoing interface, if the tap interface would be faster enabled as the pcap-bridge - and this would no work. The name for tuntap can be empty, if have only one TAP-Win32 installed (typically). Your problem with GCC 4.1 and GCC 4.2 I not understand. The current devel allows both compilers to compile your kernel. We checking the GCC-ABI. If you have an old kernel without ABI-check, then we check the GCC version. This is perhaps, you have. You should not start an old kernel binary with new daemons. Linux kernel (vmlinux) and the Linux driver have dependencies. This, we try to manage with ABI- and API- check. But, we have no backports to old versions. So, the linux kernel should build with a recent kernel patch from same source of windows driver and daemons. To solve this: Rebuild the Linux kernel with fresh patch set, your kernel config and your favorite gcc (3.3.1 ... 4.2.x). Than the devel-coLinux-20071203.exe should also be usable for you. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-01-02 20:21 Message: Logged In: NO That's no problem of CoLinux but debian. Debian assigns a new etherdevice for every new MAC. If you don't tell CoLinux to use a specific AM it will choose a random on every start... eth16 indicates, you have tried 16 times ,-) See thread "No network anmore?" Dec 8th., 2007 #cat /proc/net/dev shows an eth device number greater eth0, incremented with each boot. The effect is (currently) only seen o Workarround: 1st step: Assign a fixed MAC address in the colinux config: For example: eth0=pcap-bridge,,0A:C0:71:65:08:00, (implicit ethernet device is not recommanded) eth0=pcap-bridge,"WindowsNameOfYourEthernet",0A:C0:71:65:08:00, eth0=tuntap,LAN-TAP Vqe8(colinux),0A:C0:71:65:08:00, Attention: The "second" nibble (from left) should/must have only the values 2,6,A or E. The remainder does not matter as long as it is unique in your LAN. 2nd step: remove all entries in "/etc/udev/rules.d/z25_persistent-net.rules" like these: SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:ff:06:be:41:00", NAME="eth0" # PCI device 0x1a55:0x0005 (conet) SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:ff:25:e6:00:00",NAME="eth1" (Typically the file is empty except the comment header) HTH. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-01-02 02:54 Message: Logged In: NO The problem is: Debian is *trying* to be smart. Every time CoLinux starts up, it automatically generates a new MAC address for each adapter, seen here in your log: configured TAP at '' device as eth0 MAC address: auto generated configured PCAP bridge at '' device as eth1 MAC address: auto generated configured Slirp as eth2 MAC address: auto generated Every time a new MAC address is generated, debian will rename your ethX device. Set a MAC address for each adapter in your CoLinux config file and clear out debian's previous failed network connections. -- Kamilion ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-01-02 02:10 Message: Logged In: NO I tried running "devel-coLinux-20071203.exe" again (and letting it overwrite C:\coLinux). I then used these (minimal) commands from the DOS prompt: cd C:\coLinux colinux-daemon kernel=vmlinux-29 cobd0=Debian-3.0r2.ext3-mit-backports.14gb hda1=:cobd0 root=/dev/cobd0 eth0=tuntap After coLinux boots and I sign in I can type "ifconfig" and here is what it says: #ifconfig eth16 Link encap:Ethernet HWaddr 00:... ... lo Link encap:Local Loopback ... So it does not start at eth0 but it should. Normally (for my setup) I would start at eth0 and have eth1, eth2, sit0, and lo too. I wonder if there is a patch issue. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1861876&group_id=98788 |
|
From: SourceForge.net <no...@so...> - 2009-06-29 18:25:04
|
Support Requests item #1923750, was opened at 2008-03-23 19:39 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622064&aid=1923750&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Install Problem (example) Group: None Status: Open Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) >Summary: Networking problems (increment network adpters on boot) Initial Comment: colinux: 0.7.3 kernel: 2.6.22.18 I have a dual boot WinXP Pro SP2 and OpenSUSE 10.2. I try to use Colinux with SUSE. I created file settings.txt: mem=512 root=/dev/cobd4 kernel=vmlinux cobd3=\Device\Harddisk0\Partition3 cobd4=\Device\Harddisk0\Partition4 eth0=tuntap eth1=slirp At this time of my works, I have a device eth47 and eth48. After boot, the eth device appear to be increase by one or two or any number, base to the number of network device in the file settings.txt. I can add manually eth0 and eth1, but I can't ifup it. eth45 and eth46 appear automatically, no ifup necessary,when I use ifconfig -a. Thanks for help ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2009-06-29 20:25 Message: To allow dual boot you can bypass the rename only for coLinux by adding a line with DRIVER "conet" to the file net_persistent_names.rules some there in top of file where other skips exist: # ignore "conet" interfaces DRIVERS=="conet" GOTO="persistent_net_generator_end" For Debian 4.0 insert the '+' marked lines into file /etc/udev/rules.d/z45_persistent-net-generator.rules near line 15: ` # ignore "secondary" raw interfaces of the madwifi driver KERNEL=="ath*", ATTRS{type}=="802", GOTO="persistent_net_generator_end" + +# ignore "conet" interfaces +DRIVERS=="conet", GOTO="persistent_net_generator_end" + # provide nice comments for the generated rules SUBSYSTEMS=="pci", \ ENV{COMMENT}="PCI device $attr{vendor}:$attr{device}" ` For Ubuntu 8.1 insert '+' marked lines into file /etc/udev/rules.d/75-persistent-net-generator.rules at line 26: ` # ignore Xen virtual interfaces SUBSYSTEMS=="xen", GOTO="persistent_net_generator_end" + +# Do not rename coLinux network devices +DRIVERS=="conet", GOTO="persistent_net_generator_end" + # read MAC address ENV{MATCHADDR}="$attr{address}" ` ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-03-26 02:53 Message: Logged In: NO In file /etc/udev/rules.d/30-net_persistent_names.rules, I founded more than 40 lines like this: SUBSYSTEM=="net",ACTION=="add",... I deleted all lines. In file /etc/udev/rules.d/31-network.rules I commented the lines: SUBSYSTEM=="net",ACTION=="add",ENV(RENAMED)!= "yes",IMPORT="/lib/udev/rename_netiface %k" This two things fix my problems. Thanks. ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-03-24 20:30 Message: Logged In: YES user_id=579204 Originator: NO In the file /etc/udev/rules.d/70-persistent-net.rules needs to remove all such lines: SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:11:22:33:44:55", NAME="eth0" After the next reboot should have eth0 and eth1 and no increasing any more. But, I not understand why a change in the 0.7.3 doesn't fix the increasing networks. Version 0.7.3 build after 2008-03-02 (SVN r932) should fix it. Please check this registry key: [HKEY_CURRENT_USER\Software\coLinux\monitor\M\ethX] "mac"="00:ff:XX:XX:XX:XX" (M=Monitor number, X=network device number) Exist such registry key? Or do you used an older build? (please version check with "uname -a") ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2008-03-24 17:35 Message: Logged In: YES user_id=579204 Originator: NO It's the same as in https://sourceforge.net/tracker/index.php?func=detail&aid=1861876&group_id=98788&atid=622063 Without MAC, SuSE detects *new* cards on every boot. You needs to set unique MAC for every ethX device. Than search for saved networks in files under /etc. I don't know where it is. But, SuSE also save every new MAC in one file. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622064&aid=1923750&group_id=98788 |
81 messages has been excluded from this view by a project administrator.
