From: Wisut H. <wi...@gm...> - 2007-01-23 10:44:22
|
I do install coLinux-0.7.1-20070101 with default option and run "colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0" from the command prompt . coLinux is running fine. I can see the initrd file system and do "ls", "cd" command and so on. BUT after call "halt" command it is seem that coLinux was shutdown. I saw something like "System Halted" and then suddenly there is BLUE SCREEN of death say some thing like STOP: 0x0000008e (0xC0000046 .... I wish I can provide you more infomation but I don't know how to do. Please suggess me the way to capture the error if you want it. Error always happen after "halt" command was called. I am using windows vista rtm ultimate edition. Wisut. |
From: Holger K. <hol...@gm...> - 2007-01-23 11:21:25
|
Wisut Hantanong schrieb: > I do install coLinux-0.7.1-20070101 with default option and run > > "colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0" > root=/dev/ram0 seems a little odd. What do you expect to be there? Usually you would have something like: root=/dev/cobd0 cobd0=E:\colinux_test\filesystem.img |
From: Holger K. <hol...@gm...> - 2007-01-23 11:54:00
|
Henry Nestler schrieb: > Holger Krull wrote: >> Wisut Hantanong schrieb: >>> I do install coLinux-0.7.1-20070101 with default option and run >>> >>> "colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0" >>> >> >> root=/dev/ram0 seems a little odd. What do you expect to be there? >> >> Usually you would have something like: >> root=/dev/cobd0 >> cobd0=E:\colinux_test\filesystem.img > > initrd=initrd.gz root=/dev/ram0 > is ok for running a minimal linux from intrd. The root filesystem is > the initrd self. > Then i guess, this is the nx-Bit problem. Wisut, which processor do you use? |
From: George P B. <geo...@gm...> - 2007-03-10 20:53:00
|
Holger Krull wrote: > Henry Nestler schrieb: > >> Holger Krull wrote: >> >>> Wisut Hantanong schrieb: >>> >>>> I do install coLinux-0.7.1-20070101 with default option and run >>>> >>>> "colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0" >>>> >>>> >>> root=/dev/ram0 seems a little odd. What do you expect to be there? >>> >>> Usually you would have something like: >>> root=/dev/cobd0 >>> cobd0=E:\colinux_test\filesystem.img >>> >> initrd=initrd.gz root=/dev/ram0 >> is ok for running a minimal linux from intrd. The root filesystem is >> the initrd self. >> >> > Then i guess, this is the nx-Bit problem. > Wisut, which processor do you use? > Not really. I was able to confirm the problem on our Vista test machine which is pre nx-Bit hardware. I was able to duplicate the problem, even after exempting coLinux binaries from Vista's 'software' nx-Bit functionality. :( Looks like we have a real problem here. :( George |
From: Henry N. <Hen...@Ar...> - 2007-01-23 11:48:50
|
Holger Krull wrote: > Wisut Hantanong schrieb: >> I do install coLinux-0.7.1-20070101 with default option and run >> >> "colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0" >> > > root=/dev/ram0 seems a little odd. What do you expect to be there? > > Usually you would have something like: > root=/dev/cobd0 > cobd0=E:\colinux_test\filesystem.img initrd=initrd.gz root=/dev/ram0 is ok for running a minimal linux from intrd. The root filesystem is the initrd self. -- Henry Nestler |
From: Wisut H. <wi...@gm...> - 2007-01-25 03:51:38
|
I think I should share this ugly workaround to the group. And yes the halt problem exist only under Vista. I do try the same on my laptop with windows xp and there is no problem. Thank to Norton Ghost allowed me to restore my Vista without reinstalling. This kind of mess is what normally happened when you move to Vista. I wish you make coLinux be a Vista Ready soon. :) Wisut Hantanong On 1/24/07, Henry Nestler <Hen...@ar...> wrote: > Wisut Hantanong wrote: > > Sorry if I make you confuse. The JPG file is from my P4 desktop. Other > > files are from my laptop. > > > > Unfortunately I have no much time to try coLinux. Now I (have to) am > > using Virtual PC 2007 Beta instead for my working. Because I don't > > want to back to windows XP. coLinux on my XP has no problem. > > > > FYI I use linux to develop the embedded system firmware so I only need > > the linux's core system and some tools (gcc, tftp, telnet, ...) in my > > work. And I can tell you that you make a wonderful linux framework. I > > found that your coLinux is faster than one in VPC. :) > > I use coLinux for developing embedded systems at work. > http://www.ssv-embedded.de/ssv/english/home.htm > http://www.terminal-systems.de/colinux1.htm (sorry german only) > > > Now I am deciding between working in coLinux without "halt" command or > > use one VPC. I hate killing colinux-daemon without calling "poweroff, > > init 0, halt". > > > > Hope you can fix this little mess soon. > > For a ugly workarrount: Locate the "halt" or real "poweroff" in the > initscripts. There are mostly some steps with "umount ... sync .. mount > / -o ro". After this insert two lines: > echo "colinux halt now, or press ENTER" > read junk > Than you can shutdown without real power off and kill the colinux-daemon > after yousee the message. CoLinux you can terminate in the FLTK menu. > > Can you say: The halt problem exist only under Vista? > I will install it again and check next weekend. > > > In future if you want to chat with me online, I am on windows live > > messenger with contact ##### > > I have no such accounts. I'm more offline. > > -- > Henry Nestler > |
From: George P B. <geo...@gm...> - 2007-01-26 03:04:36
|
I think I had similiar problems testing on Vista. I think I solved it by adding colinux-daemon.exe and linux.sys to the Vista's Software DEP exception list. I forget where that's at speifically, but it's like under start-up options or something. Have you tried that? George On 1/23/07, Wisut Hantanong <wi...@gm...> wrote: > I do install coLinux-0.7.1-20070101 with default option and run > > "colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0" > > from the command prompt . coLinux is running fine. I can see the > initrd file system and do "ls", "cd" command and so on. > > BUT after call "halt" command it is seem that coLinux was shutdown. I > saw something like "System Halted" and then suddenly there is BLUE > SCREEN of death say some thing like > > STOP: 0x0000008e (0xC0000046 .... > > I wish I can provide you more infomation but I don't know how to do. > Please suggess me the way to capture the error if you want it. > > Error always happen after "halt" command was called. > I am using windows vista rtm ultimate edition. > > Wisut. > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > -- George |
From: Wisut H. <wi...@gm...> - 2007-01-26 04:53:55
|
Add colinux-daemon to DEP exception don't solve my problem. What colinux version are you using in vista ? Can you write a step-by-step installation guide for me ? Have you ever try calling "colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0" (it will boot to the initrd system with busybox shell) and then "halt" in that linux shell ? On 1/26/07, George P Boutwell <geo...@gm...> wrote: > I think I had similiar problems testing on Vista. I think I solved it > by adding colinux-daemon.exe and linux.sys to the Vista's Software DEP > exception list. I forget where that's at speifically, but it's like > under start-up options or something. > > Have you tried that? > > George > > On 1/23/07, Wisut Hantanong <wi...@gm...> wrote: > > I do install coLinux-0.7.1-20070101 with default option and run > > > > "colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0" > > > > from the command prompt . coLinux is running fine. I can see the > > initrd file system and do "ls", "cd" command and so on. > > > > BUT after call "halt" command it is seem that coLinux was shutdown. I > > saw something like "System Halted" and then suddenly there is BLUE > > SCREEN of death say some thing like > > > > STOP: 0x0000008e (0xC0000046 .... > > > > I wish I can provide you more infomation but I don't know how to do. > > Please suggess me the way to capture the error if you want it. > > > > Error always happen after "halt" command was called. > > I am using windows vista rtm ultimate edition. > > > > Wisut. > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share your > > opinions on IT & business topics through brief surveys - and earn cash > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > > coLinux-users mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-users > > > > > -- > George > |