From: Jurgis <ju...@em...> - 2009-03-21 21:05:49
Attachments:
trace.txt
|
Hi! I can not start coLinux, I have tried all possible I could find: - coLinux 0.7.3 - andLinux - Ulteo Open Virtual Desktop They all use coLinux and it does not start The last try was - I downloaded the latest snapshot and run this command > colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0 -v 1 The result is allways the same. I have never gone past this line: PID hash table entries: 2048 (order: 11, 8192 bytes) ------------------------------------------------------------------- Cooperative Linux Daemon, 0.8.0 Daemon compiled on Thu Mar 19 19:47:12 2009 using 'vmlinux' as kernel image using 'initrd.gz' as initrd image mapping cofs31 to \??\D:\programs\coLinux kernel boot parameters: 'root=/dev/ram0' PID: 1820 colinux: launching console colinux: booting Linux version 2.6.22.18-co-0.8.0 (hn@hn-dt) (gcc version 4.2.1 (SUSE Linux)) #1 PREEMPT Thu Mar 19 19:45:43 UTC 2009 512MB LOWMEM available. initrd enabled: start: 0xdff9a000 size: 0x00065881 Entering add_active_range(0, 0, 131072) 0 entries of 256 used Zone PFN ranges: DMA 0 -> 0 Normal 0 -> 131072 early_node_map[1] active PFN ranges 0: 0 -> 131072 On node 0 totalpages: 131072 DMA zone: 0 pages used for memmap Normal zone: 1024 pages used for memmap Normal zone: 130048 pages, LIFO batch:31 Built 1 zonelists. Total pages: 130048 Kernel command line: root=/dev/ram0 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 Setting proxy interrupt vectors PID hash table entries: 2048 (order: 11, 8192 bytes) -------------------------------------------------------- I have Windows XP SP3 Intel Core Duo T2250 @ 1.73Ghz 2GB RAM Is there anything more I can do to help locating the problem? I also run > colinux-debug-daemon.exe -d -f trace.txt and attached the trace file. Any help would be appreciated. Jurgis |
From: Henry N. <hen...@ar...> - 2009-03-21 23:14:57
|
Hello Jurgis, Jurgis wrote: > I can not start coLinux, I have tried all possible I could find: > - coLinux 0.7.3 > - andLinux > - Ulteo Open Virtual Desktop > They all use coLinux and it does not start > > The last try was - I downloaded the latest snapshot and > run this command > > colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0 -v 1 > > The result is allways the same. > I have never gone past this line: PID hash table entries: 2048 (order: > 11, 8192 bytes) > > ------------------------------------------------------------------- > Cooperative Linux Daemon, 0.8.0 > Daemon compiled on Thu Mar 19 19:47:12 2009 > > using 'vmlinux' as kernel image > using 'initrd.gz' as initrd image > mapping cofs31 to \??\D:\programs\coLinux > kernel boot parameters: 'root=/dev/ram0' > PID: 1820 > colinux: launching console > colinux: booting > Linux version 2.6.22.18-co-0.8.0 (hn@hn-dt) (gcc version 4.2.1 (SUSE > Linux)) #1 PREEMPT Thu Mar 19 19:45:43 UTC 2009 > 512MB LOWMEM available. > initrd enabled: start: 0xdff9a000 size: 0x00065881 > [...] > Initializing CPU#0 > Setting proxy interrupt vectors > PID hash table entries: 2048 (order: 11, 8192 bytes) The next line should be the init message from console: "Console: colour CoCON 80x25" > I have Windows XP SP3 > Intel Core Duo T2250 @ 1.73Ghz > 2GB RAM > > Is there anything more I can do to help locating the problem? > I also run > > colinux-debug-daemon.exe -d -f trace.txt > and attached the trace file. With "colinux-debug-daemon.exe -d -p -f trace.xml" the output would read better. You can convert it with "colinux-debug-daemon.exe -p <trace.txt >trace.xml" But it contains non interestings as we can see from colinux-daemon output: using 'vmlinux' as kernel image using 'initrd.gz' as initrd image mapping cofs31 to \??\D:\programs\coLinux kernel boot parameters: 'root=/dev/ram0' colinux: launching console Please try a higher debug level: colinux-debug-daemon.exe -d -p -s prints=31,misc=31 -f debug.xml More about debugging finds in file "debugging.txt" in your installation, or online here: http://colinux.svn.sourceforge.net/svnroot/colinux/branches/devel/doc/debugging For your problem I can not see a solution currently. How ends the colinux-daemon.exe? Is it back to prompt? Or hangs it? Exist the file "colinux-console-fltk.exe"? Is it launched? Can you see the "Cooperative Linux Console" Window, like this: http://colinux.wikia.com/wiki/Image:CoLinux-fltk-console-0.7.3.png If not, can you execute colinux-console-fltk.exe manualy? -- Henry N. |
From: Jurgis <ju...@em...> - 2009-03-22 11:15:20
|
Henry, Thank you for the provided information! I have run following commands > colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0 -v 1 > colinux-debug-daemon.exe -d -p -s prints=31,misc=31 -f debug.xml The results (2 screenshots and debug.xml file) can be found here: http://jurgis.emails.lv/colinux/01/ I'm still using devel-coLinux-20090319.exe When running colinux-daemon.exe it does not end normally, I have to click on the cross at the right upper corner to close it. Regards, Jurgis Henry Nestler wrote: > Hello Jurgis, > > Jurgis wrote: >> I can not start coLinux, I have tried all possible I could find: >> - coLinux 0.7.3 >> - andLinux >> - Ulteo Open Virtual Desktop >> They all use coLinux and it does not start >> >> The last try was - I downloaded the latest snapshot and >> run this command >> > colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0 -v 1 >> >> The result is allways the same. >> I have never gone past this line: PID hash table entries: 2048 (order: >> 11, 8192 bytes) >> >> ------------------------------------------------------------------- >> Cooperative Linux Daemon, 0.8.0 >> Daemon compiled on Thu Mar 19 19:47:12 2009 >> >> using 'vmlinux' as kernel image >> using 'initrd.gz' as initrd image >> mapping cofs31 to \??\D:\programs\coLinux >> kernel boot parameters: 'root=/dev/ram0' >> PID: 1820 >> colinux: launching console >> colinux: booting >> Linux version 2.6.22.18-co-0.8.0 (hn@hn-dt) (gcc version 4.2.1 (SUSE >> Linux)) #1 PREEMPT Thu Mar 19 19:45:43 UTC 2009 >> 512MB LOWMEM available. >> initrd enabled: start: 0xdff9a000 size: 0x00065881 >> [...] >> Initializing CPU#0 >> Setting proxy interrupt vectors >> PID hash table entries: 2048 (order: 11, 8192 bytes) > > The next line should be the init message from console: > "Console: colour CoCON 80x25" > >> I have Windows XP SP3 >> Intel Core Duo T2250 @ 1.73Ghz >> 2GB RAM >> >> Is there anything more I can do to help locating the problem? >> I also run >> > colinux-debug-daemon.exe -d -f trace.txt >> and attached the trace file. > > With "colinux-debug-daemon.exe -d -p -f trace.xml" the output would > read better. > You can convert it with "colinux-debug-daemon.exe -p <trace.txt > >trace.xml" > But it contains non interestings as we can see from colinux-daemon > output: > using 'vmlinux' as kernel image > using 'initrd.gz' as initrd image > mapping cofs31 to \??\D:\programs\coLinux > kernel boot parameters: 'root=/dev/ram0' > colinux: launching console > > Please try a higher debug level: > colinux-debug-daemon.exe -d -p -s prints=31,misc=31 -f debug.xml > More about debugging finds in file "debugging.txt" in your > installation, or online here: > http://colinux.svn.sourceforge.net/svnroot/colinux/branches/devel/doc/debugging > > > For your problem I can not see a solution currently. > > How ends the colinux-daemon.exe? Is it back to prompt? Or hangs it? > > Exist the file "colinux-console-fltk.exe"? > Is it launched? Can you see the "Cooperative Linux Console" Window, > like this: > http://colinux.wikia.com/wiki/Image:CoLinux-fltk-console-0.7.3.png > If not, can you execute colinux-console-fltk.exe manualy? > |
From: Henry N. <hen...@ar...> - 2009-03-22 22:15:22
|
Am 22.03.2009 08:16, schrieb Jurgis: > Henry, > > Thank you for the provided information! > > I have run following commands and attached screenshots and debug.xml file. > > colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0 -v 1 > > colinux-debug-daemon.exe -d -p -s prints=31,misc=31 -f debug.xml > > I'm still using devel-coLinux-20090319.exe > > When running colinux-daemon.exe it does not end normally, I have to click > on the cross at the right upper corner to close it. Sorry, the debug have not more helpfully informations. I think, it's a problem with timer. The next boot step after "pidhash_init" (your last line) will setup the timer source for coLinux kernel. That is very hard to debug. I feel this PC has one of the special timer chip, that we don't handle right. Please view the older mail: http://www.nabble.com/forum/ViewPost.jtp?post=18019511&framed=y Boot with a Live CD, for example Knoppix or Gparted and watch for such kernel boot message: "MP-BIOS bug: 8254 timer not connected to IO-APIC" -- Henry N. |
From: Paolo M. <pao...@gm...> - 2009-03-23 07:34:53
|
Hi Jurgis, I have a small win32 driver that counts interrupts. It does not change anything and it is removed cleanly after the end. If you run it, we can have some more information. Let me know if you are interested to try it. Bye, Paolo On Sun, Mar 22, 2009 at 11:15 PM, Henry Nestler <hen...@ar...> wrote: > Am 22.03.2009 08:16, schrieb Jurgis: >> Henry, >> >> Thank you for the provided information! >> >> I have run following commands and attached screenshots and debug.xml file. >> > colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0 -v 1 >> > colinux-debug-daemon.exe -d -p -s prints=31,misc=31 -f debug.xml >> >> I'm still using devel-coLinux-20090319.exe >> >> When running colinux-daemon.exe it does not end normally, I have to click >> on the cross at the right upper corner to close it. > > Sorry, the debug have not more helpfully informations. > > I think, it's a problem with timer. The next boot step after > "pidhash_init" (your last line) will setup the timer source for coLinux > kernel. That is very hard to debug. I feel this PC has one of the > special timer chip, that we don't handle right. > > Please view the older mail: > http://www.nabble.com/forum/ViewPost.jtp?post=18019511&framed=y > > Boot with a Live CD, for example Knoppix or Gparted and watch for such > kernel boot message: "MP-BIOS bug: 8254 timer not connected to IO-APIC" > > -- > Henry N. > > ------------------------------------------------------------------------------ > Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are > powering Web 2.0 with engaging, cross-platform capabilities. Quickly and > easily build your RIAs with Flex Builder, the Eclipse(TM)based development > software that enables intelligent coding and step-through debugging. > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
From: Jurgis <ju...@em...> - 2009-03-23 11:22:54
|
Hi Paolo, Here are DebugView results: http://jurgis.emails.lv/colinux/03/DebugView.txt Jurgis Paolo Minazzi wrote: > Hi Jurgis, > I have a small win32 driver that counts interrupts. > It does not change anything and it is removed cleanly after the end. > If you run it, we can have some more information. > Let me know if you are interested to try it. > Bye, > Paolo > > > > On Sun, Mar 22, 2009 at 11:15 PM, Henry Nestler <hen...@ar...> wrote: > >> Am 22.03.2009 08:16, schrieb Jurgis: >> >>> Henry, >>> >>> Thank you for the provided information! >>> >>> I have run following commands and attached screenshots and debug.xml file. >>> > colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0 -v 1 >>> > colinux-debug-daemon.exe -d -p -s prints=31,misc=31 -f debug.xml >>> >>> I'm still using devel-coLinux-20090319.exe >>> >>> When running colinux-daemon.exe it does not end normally, I have to click >>> on the cross at the right upper corner to close it. >>> >> Sorry, the debug have not more helpfully informations. >> >> I think, it's a problem with timer. The next boot step after >> "pidhash_init" (your last line) will setup the timer source for coLinux >> kernel. That is very hard to debug. I feel this PC has one of the >> special timer chip, that we don't handle right. >> >> Please view the older mail: >> http://www.nabble.com/forum/ViewPost.jtp?post=18019511&framed=y >> >> Boot with a Live CD, for example Knoppix or Gparted and watch for such >> kernel boot message: "MP-BIOS bug: 8254 timer not connected to IO-APIC" >> >> -- >> Henry N. >> >> ------------------------------------------------------------------------------ >> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are >> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and >> easily build your RIAs with Flex Builder, the Eclipse(TM)based development >> software that enables intelligent coding and step-through debugging. >> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com >> _______________________________________________ >> coLinux-users mailing list >> coL...@li... >> https://lists.sourceforge.net/lists/listinfo/colinux-users >> >> |
From: Jurgis <ju...@em...> - 2009-03-23 11:18:24
|
Henry, Thank you for such a thorough descriptions of all the steps! Here are the results: http://jurgis.emails.lv/colinux/02/ Jurgis Henry Nestler wrote: > Am 22.03.2009 23:15, schrieb Henry Nestler: >> Am 22.03.2009 08:16, schrieb Jurgis: >>> Henry, >>> >>> Thank you for the provided information! >>> >>> I have run following commands and attached screenshots and debug.xml >>> file. >>> > colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0 >>> -v 1 >>> > colinux-debug-daemon.exe -d -p -s prints=31,misc=31 -f debug.xml >>> >>> I'm still using devel-coLinux-20090319.exe >>> >>> When running colinux-daemon.exe it does not end normally, I have to >>> click >>> on the cross at the right upper corner to close it. >> >> Sorry, the debug have not more helpfully informations. >> >> I think, it's a problem with timer. The next boot step after >> "pidhash_init" (your last line) will setup the timer source for coLinux >> kernel. That is very hard to debug. I feel this PC has one of the >> special timer chip, that we don't handle right. >> >> Please view the older mail: >> http://www.nabble.com/forum/ViewPost.jtp?post=18019511&framed=y >> >> Boot with a Live CD, for example Knoppix or Gparted and watch for such >> kernel boot message: "MP-BIOS bug: 8254 timer not connected to IO-APIC" >> > > It would be nice, if you can send me kernel boot messages from such > live cd. > Run "dmesg >/mesg.txt" to store the messages in file, and please the > list of interrupts under this native Linux ("cat /proc/interrupts > >interrupts.txt") > > And under Windows please send me the list of interrupts. You will find > this by running > "C:\Program files\Shared files\Microsoft Shared\MsInfo\msinfo32.exe" > and selecting Hardwareresource IRQs. The Directory can be localized in > your language. > > To solve the problem we need to locatisate the stopping function > inside coLinux kernel. But this needs many more developing time and > special builds with more outputs between the steps to find the > stopper. I don't know how we can do this over a mail distance. That > would cost time for your testing and my coding. > |