Menu
▾
▴
colinux-devel
|
From: <my...@gm...> - 2004-01-31 19:43:19
|
First, thanks a bunch, Dan, for all of the hard work you've done. I'm looking forward for working with colinux, like many others who are following this project. I download and installed the binary files, per the instructions in the README. The TAP-Win32 driver seemed to install OK. When I try to run the colinux-daemon.exe program, I get "Error initializing the kernel driver" and it terminates with a "-1". FWIW, I'm running Windows-XP Pro. Any suggestions? Thanks, Larry. |
|
From: Dan A. <da...@gm...> - 2004-01-31 20:32:37
|
On Sat, Jan 31, 2004 at 03:03:28PM -0500, my...@gm... wrote: > First, thanks a bunch, Dan, for all of the hard work you've done. I'm > looking forward for working with colinux, like many others who are > following this project. > > I download and installed the binary files, per the instructions in the > README. The TAP-Win32 driver seemed to install OK. When I try to run the > colinux-daemon.exe program, I get "Error initializing the kernel driver" > and it terminates with a "-1". FWIW, I'm running Windows-XP Pro. Any > suggestions? Since more than one person saw this problem, I've compiled a slightly modified colinux-daemon.exe and added it to the release. Now, for the source code part of this message: It appears that an error is wrongly propagated from kernel space to user space when the driver gets initialized by the daemon. The branch that gets affected is in co_manager_init() (colinux/user/manager.c). It also appears that it doesn't happen on my setup. In the patched daemon, I changed co_manager_init() so that it would always return CO_RC_OK. With this patch, it appears that the daemon continues running on Matt's setup without other such failures. Since this is a developers mailing list, I urge you to look at the source and send me a patch :) I mean, help me debug this faster. You do want a working coLinux, right? ;). -- Dan Aloni da...@gm... |
|
From: <my...@gm...> - 2004-01-31 21:11:51
|
OK, that was different - it didn't work for me. I get a blue-screen when I run the modified colinux-daemon.exe, due to: IRQL_NOT_LESS_OR_EQUAL Larry > On Sat, Jan 31, 2004 at 03:03:28PM -0500, my...@gm... wrote: >> First, thanks a bunch, Dan, for all of the hard work you've done. I'm >> looking forward for working with colinux, like many others who are >> following this project. >> >> I download and installed the binary files, per the instructions in the >> README. The TAP-Win32 driver seemed to install OK. When I try to run the >> colinux-daemon.exe program, I get "Error initializing the kernel driver" >> and it terminates with a "-1". FWIW, I'm running Windows-XP Pro. Any >> suggestions? > > Since more than one person saw this problem, I've compiled a slightly > modified colinux-daemon.exe and added it to the release. > > Now, for the source code part of this message: > > It appears that an error is wrongly propagated from kernel space > to user space when the driver gets initialized by the daemon. The branch > that gets affected is in co_manager_init() (colinux/user/manager.c). It > also appears that it doesn't happen on my setup. > > In the patched daemon, I changed co_manager_init() so that it would > always return CO_RC_OK. With this patch, it appears that the daemon > continues running on Matt's setup without other such failures. > > Since this is a developers mailing list, I urge you to look at the > source and send me a patch :) I mean, help me debug this faster. You do > want a working coLinux, right? ;). > > -- > Dan Aloni > da...@gm... > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
|
From: ePAc <ep...@ko...> - 2004-01-31 22:25:23
|
> OK, that was different - it didn't work for me. I get a blue-screen when I > run the modified colinux-daemon.exe, due to: > > IRQL_NOT_LESS_OR_EQUAL > > Larry I got this as well, and i'm now waiting for the system to dump the whole memory. would any kind of processing on the memdump be useful to anyone ? the machine is a Dell Inspiron 5150, 1.6Ghz, P4, 512M ram, and enough HD to have a couple more full mem dumps... Let me know... Jok --- Nothing is foolproof to a sufficiently talented fool... oo ,(..)\ ~~ |
|
From: Dan A. <da...@gm...> - 2004-01-31 22:34:01
|
On Sat, Jan 31, 2004 at 02:25:45PM -0800, ePAc wrote: > > OK, that was different - it didn't work for me. I get a blue-screen when I > > run the modified colinux-daemon.exe, due to: > > > > IRQL_NOT_LESS_OR_EQUAL > > > > Larry > > I got this as well, and i'm now waiting for the system to dump the whole > memory. would any kind of processing on the memdump be useful to anyone ? These memory dumps sound useful. Do you know some reference about how to enable them and other info that might be useful? -- Dan Aloni da...@gm... |
|
From: ePAc <ep...@ko...> - 2004-01-31 22:54:31
|
> > > IRQL_NOT_LESS_OR_EQUAL > > > > > > Larry > > > > I got this as well, and i'm now waiting for the system to dump the whole > > memory. would any kind of processing on the memdump be useful to anyone ? > > These memory dumps sound useful. Do you know some reference about how to > enable them and other info that might be useful? right click on "My Computer" select "Properties" select "Advanced" tab under "Startup And Recovery" there is some option to setup different type of memory dump (minidump, kernel dump, full memory dump). i had mine setup as "Full Memory Dump" (512M). as for analysis, there used to be some tools on the MS web site, i'll track those down. DebugView was able to "process" that memdump and give me 3 messages: 1 - 2:06:06 PM - Driver Unloaded (*) 2 - 2:07:38 PM - Driver Loaded 3 - 2:07:38 PM - Allocated cmon0 (*) might be from the first attempt for which Memdump wasn't enabled during the previous boot or something [/me clueless]... this was running under XP. Have you done any kind of testing with XP ? or was it all win2k ? my other machine (win2K) is loading properly, and the console is coming up, and i'm having the same set of problem with the e2fsck (i will write down those numbers next time). All in all, "This is fantastic !"(TM). You have now access to probably a couple dozen different config (mine included) which will allow us all to run linux on our poor windows machine :o) is there anyone on the list who has access to the newer DDK (2003/XP version), and that could compile the linux.sys with that OS. It would make sense that the linux.sys driver need to be compiled for the proper target OS. is there any success on XP ? Thanks, Jok --- Nothing is foolproof to a sufficiently talented fool... oo ,(..)\ ~~ |
|
From: Tony H. <tm...@no...> - 2004-01-31 23:05:20
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ePAc wrote: | is there anyone on the list who has access to the newer DDK (2003/XP | version), and that could compile the linux.sys with that OS. It would make | sense that the linux.sys driver need to be compiled for the proper target | OS. is there any success on XP ? In theory I've got access to it but not enough disk space to install it. ~ I doubt that's the problem though as from the readme the compilation is done under cygwin and just the final link is done using the DDK. It's possible, though, that cygwin is making some assumption about userspace that's simply not true at the driver level... compiling the source under visual studio might be worth it. Tony -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFAHDSf5UdHDk9LaRcRArJdAJ4wDZMHEAXyl5wCDR9lkGEELbjAhACePzzO 4GIaHqJEOwHbobC3hW7zpMQ= =LE8u -----END PGP SIGNATURE----- |
|
From: Dan A. <da...@gm...> - 2004-01-31 21:19:49
|
On Sat, Jan 31, 2004 at 04:32:01PM -0500, my...@gm... wrote: > OK, that was different - it didn't work for me. I get a blue-screen when I > run the modified colinux-daemon.exe, due to: > > IRQL_NOT_LESS_OR_EQUAL This is bug I'm haunting for awhile, but I haven't managed to reproduce it with my computers. I'm not sure what causes this, but it is possible that some hardware configurations are responsible. If you have some Windows kernel debugging experience or know anyone who does and can help, please tell. -- Dan Aloni da...@gm... |
|
From: <my...@gm...> - 2004-01-31 21:28:04
|
Well, its definitely repeatable on my machine! I'm using Windows XP-Pro on a Dell Inspiron 2650 Notebook, if that helps. I haven't done any Windows Kernel debugging before, but I'll see what I can come up with. Larry. > On Sat, Jan 31, 2004 at 04:32:01PM -0500, my...@gm... wrote: >> OK, that was different - it didn't work for me. I get a blue-screen when >> I >> run the modified colinux-daemon.exe, due to: >> >> IRQL_NOT_LESS_OR_EQUAL > > This is bug I'm haunting for awhile, but I haven't managed to reproduce > it with my computers. I'm not sure what causes this, but it is possible > that some hardware configurations are responsible. > > If you have some Windows kernel debugging experience or know anyone who > does and can help, please tell. > > -- > Dan Aloni > da...@gm... > |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X