#15 Cannot startup

closed
nobody
None
5
2007-11-21
2005-05-10
VooDooMan
No

Hello,

coLinux freezes on startup. This is log from console:

Cooperative Linux Daemon, 0.6.2
Compiled on Sat Feb 5 10:19:28 2005

Linux version 2.6.10-co-0.6.2 (karrde@callisto.yi.org)
(gcc version 3.3.5 (Debia
n 1:3.3.5-8)) #5 Sat Feb 5 10:19:16 IST 2005
128MB LOWMEM available.
initrd enabled: start: 0xc7ea2000 size: 0x0015db27)
On node 0 totalpages: 32768
DMA zone: 0 pages, LIFO batch:1
Normal zone: 32768 pages, LIFO batch:8
HighMem zone: 0 pages, LIFO batch:1
Built 1 zonelists
Kernel command line: root=/dev/cobd0
Initializing CPU#0
Setting proxy interrupt vectors
PID hash table entries: 1024 (order: 10, 16384 bytes)
Using cooperative for high-res timesource
searching TAP device named "CoLinux"
found TAP device named "CoLinux"
opening TAP: "CoLinux"
driver version 8.1
enabling TAP...
Console: colour CoCON 80x25

Using windows 2000 server

Regards,
VooDooMan

Discussion

  • VooDooMan
    VooDooMan
    2005-05-10

    Configuration file

     
    Attachments
  • Logged In: YES
    user_id=30412

    What was your command-line like? Sounds like it didn't open
    the console, are coLinux prcoesses running in the task manager?

     
  • Logged In: YES
    user_id=30412

    Changed this to a support request as it's probably not a
    bug. VoodDooMan... What was the command-line that you used
    to run colinux?

     
  • VooDooMan
    VooDooMan
    2005-06-23

    censored screenshot of my screen when it is frozen

     
    Attachments
  • VooDooMan
    VooDooMan
    2005-06-23

    processes in process explorer (list of tasks)

     
    Attachments
  • VooDooMan
    VooDooMan
    2005-06-23

    Logged In: YES
    user_id=1049792

    Hello,

    I am really very sorry, but i forgot about this problem.
    Please see my new two attachments as i have added them here,
    it is screen shot of frozen CoLinux, and screen shot with my
    task list (where you can see also command line arguments).

    tu start it up, i am using this "fc1.cmd" script:

    ---
    C:
    cd "\vdm\Program Files\coLinux\"
    colinux-daemon.exe -c D:\vdm\VM\coLinux\fc1\fc1.xml
    pause
    ---
    which is located: D:\vdm\VM\coLinux\fc1\fc1.cmd
    and in dir D:\vdm\VM\coLinux\fc1\ there are disk image
    files, and fc1.xml contains:
    ...path="\DosDevices\d:\vdm\VM\coLinux\fc1\fc1_2GB_root"
    ...
    ---path="\DosDevices\d:\vdm\VM\coLinux\fc1\swap_device"
    and installation path of CoLinux binaries is:
    C:\vdm\Program Files\coLinux\ , so i am pretty sure that there is no problem with
    errorneous path (no typo in configs and other files' paths)

    Hope this help.

    Regards,
    VooDooMan

     
  • VooDooMan
    VooDooMan
    2005-06-23

    Logged In: YES
    user_id=1049792

    Hello again,

    Note in attachment with screenshot of TASK LIST, there is
    process

    colinux-daemon.exe

    consuming CPU varying from 30 to 63 percent, while it is
    frozen.

    Regards,
    VooDooMan

     
  • Logged In: YES
    user_id=30412

    Hmm... Well it's not what I thought it was. Maybe it's an
    configuration problem in the image you are using? Can you
    try adding to the bootparams section of your XML file 'single' :

    <bootparams>root=/dev/cobd0 single</bootparams>

    And see if it boots?

    George

     
  • VooDooMan
    VooDooMan
    2005-06-23

    Logged In: YES
    user_id=1049792

    Hello,

    the behaviour is same.

    Please, could you send me "testing" build of CoLinux (win32
    binaries, or just .EXE's) which writes verbose log to text
    file - e.g. after each significant event between
    initalization and boot itself (call it "checkpoint") writes
    something to log, to see where is it hanging. Just something
    like
    fprintf(f,"%d\n",test++);
    i will send it back to you, because i am missing CoLinux and
    hateing M$ V*****l PC 2004, and i am affraid that someone
    has the same problem... i would be very glad if i helped you
    to resolve this weird problem.

    Regards,
    VooDooMan

    e-mail:
    ghostvoodooman@users.you-know-the-right-domain.net

     
  • VooDooMan
    VooDooMan
    2005-07-01

    Logged In: YES
    user_id=1049792

    PING?

     
  • VooDooMan
    VooDooMan
    2005-08-10

    Logged In: YES
    user_id=1049792

    Nevermind, I have upgraded to win2k3 server and it is
    working well. I guess it began on 2000 server after i
    installed terminal server. now, on 2003 with terminal server
    it is okay. - of course, i ran it under admin account, not
    in terminal client, but locally. I had some problems with
    DirectX - some movies that were using DivX, XviD and M$
    codecs or common movie DVD's caused to freeze the system -
    if CoLinux uses some of DirectX API's, then there would be
    the point of the problem.

    Anyways, thank you very much for great software, your expert
    work is worth to me. Keep it going on!

    Regards,
    VooDooMan

     
  • VooDooMan
    VooDooMan
    2005-12-17

    Logged In: YES
    user_id=1049792

    Hello,

    I think I got it. This happens after installing

    VMware-workstation-5.0.0-13124.exe
    MD5()==454b20e4007dd16f2173c29f0d230be2
    SHA1()==2ed6c39c52d2af59f4a99e446edfd81df255e768

    , after uninstall of VMware, it works okay again.

    Now I got Win2k3 server, and the behavior is the same.

    After uninstall, and installing

    VMware-workstation-5.5.0-18463.exe

    everything works okay.

    If you need that trial of VMware 5.0 for testing purposes,
    you can contact me by e-mail.

    Win2k3 server
    CoLinux 0.6.2 (sf.net file release version, not cvs one)

    Regards,
    VooDooMan

     
  • VooDooMan
    VooDooMan
    2005-12-17

    Logged In: YES
    user_id=1049792

    Well, I just found out that after first startup of VMware
    5.5 coLinux stopped to work, and it is same as I explained.
    I think there is some conflict with network/virtual adapters.

    I am using

    <network index="0" type="bridged" name="LAN" />

    and I have installed WinPcap 3.1, but I don't know if these
    informations are relevant and sufficient. It seems (except
    of last line "Console:...") like network problem.

    Thank you.

     
  • Henry N.
    Henry N.
    2007-11-21

    • status: open --> closed
     
  • Henry N.
    Henry N.
    2007-11-21

    Logged In: YES
    user_id=579204
    Originator: NO

    This situation is known from missing /dev/console, /dev/tty1, /dev/zero.
    The /bin/init can not write to console and still hangs.

    You should create the device node /dev/console in the loop mounted image
    and some others:

    # mknod -m 600 dev/console c 5 1
    # mknod -m 666 dev/null c 1 3 #Just in case.
    # mknod -m 666 dev/zero c 1 5

    (Other case version is out dated now.)