From: Paul M. <fka...@ya...> - 2006-02-16 16:57:08
|
Sorry for the double post; due to a misunderstanding of mailing list operation, my original post was buried inside an unrelated thread. Reposting in a new thread. ------------------------------------------------ coLinux is a fantastic idea, and I would love to be able to use it. This being my first shot at it, I tried to keep it simple. All I changed from the default 0.6.3 config is to disable the swap, increase the memory to "128" and assign the root fs to a downloaded image. Despite that, I can't get very far through the boot process before the whole machine hangs. The last message printed before it hangs is "RAMDISK: Compressed image found at block 0". I tried the /NOPAE and /noexecute=AlwaysOff kernel params, even though that's not supposed to be necessary anymore. I tried switching to the Uniprocessor kernel, even though SMP problems were supposedly worked around. (The above steps were taken AFTER coLinux was installed.) I disabled McAfee VirusScan before launching coLinux. I tried both Gentoo and Debian images. During installation, I installed WinPcap 3.1 and selected the TAP configuration. I disabled windows firewall on the new connection. I noticed that the connection icon changes before the machine hangs, like it's trying to get an address. I would like to get coLinux working, but I don't know what else to do. (Although I am getting concerned about my windows filesystem getting trashed by all these hangs - good thing it's not FAT). System Info: Windows XP Professional SP2 ACPI Multiprocessor kernel Dual pentium3 1Ghz CPU's 512M RAM VP6 VIA Apollo Pro 133A mobo I have a strange hard disk setup, but I don't think that's relevant. I dual-boot with linux, so the hardware isn't incompatible with linux or anything like that. I was not trying to access my existing linux installation from coLinux at all. Config file contents follow. <?xml version="1.0" encoding="UTF-8"?> <colinux> <!-- This line needs to point to your root file system. For example change "root_fs" to the name of the Debian image. Inside coLinux it will be /dev/cobd0 Block Device Aliasing: You can now handle most dual-boot issues by adding an alias="devname" to block_device. i.e. alias="hda", alias="hda1" You can do this for SCSI as well as IDE. You need to be aware that if you add an alias, you need to change your bootparams root="devname" appropriately (you may need to use devfs naming in some situations). --> <block_device index="0" path="\DosDevices\c:\coLinux\Debian-3.0r2.ext3-mit-backports.1gb" enabled="true" /> <!-- This line can specify a swap file if you wish, or an additional image file, it will /dev/cobd1. Additional block_devices can be specified in the same manner by increasing the index --> <!-- <block_device index="1" path="\DosDevices\c:\coLinux\swap" enabled="true" /> --> <!-- This is an experimental feature, it may not function completely. <cofs_device index="0" type="flat" path="\DosDevices\C:\" enabled="true" /> --> <!-- bootparams allows you to pass kernel boot parameters --> <bootparams>root=/dev/cobd0</bootparams> <!-- Initial RamDISK (initrd) support --> <initrd path="initrd.gz" /> <!-- image allows you to specify the kernel to boot --> <image path="vmlinux" /> <!-- this line allows you to specify the amount of memory available to coLinux --> <memory size="128" /> <!-- This allows you to modify networking parameters, see the README or website or wiki for more information --> <network index="0" type="tap" /> </colinux> __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
From: Paul M. <fka...@ya...> - 2006-02-16 17:17:10
|
I installed to c:\coLinux, and that is where the config file points. --- Wai Wu <wwu@Calltrol.com> wrote: > My bad. I run * on coLinux. Going back to topic. Did > you install it on the default directry? If you > didn't you might have to edit the config file. > -----Original Message----- From: Paul Mogren [mailto:fka...@ya...] Sent: Thursday, February 16, 2006 11:36 AM To: Wai Wu Subject: RE: [coLinux-users] 0.6.3 hangs on XP Pro SP2, SMP (newbie) I have no idea what you're talking about. This was a clean install of colinux, as I mentioned, I've never used it before. And I am not interested in running PBX software. --- Wai Wu <wwu@Calltrol.com> wrote: > Why don't you install colinux clean first. Then > download * in colinux and build it in colinux. It > tool me less than 20 minutes to get asterisk > running. > --- Paul Mogren <fka...@ya...> wrote: > Sorry for the double post; due to a misunderstanding > of mailing list operation, my original post was > buried > inside an unrelated thread. Reposting in a new > thread. > ------------------------------------------------ > > > coLinux is a fantastic idea, and I would love to be > able to use it. This being my first shot at it, I > tried to keep it simple. All I changed from the > default 0.6.3 config is to disable the swap, > increase > the memory to "128" and assign the root fs to a > downloaded image. > > Despite that, I can't get very far through the boot > process before the whole machine hangs. The last > message printed before it hangs is "RAMDISK: > Compressed image found at block 0". > > I tried the /NOPAE and /noexecute=AlwaysOff kernel > params, even though that's not supposed to be > necessary anymore. > I tried switching to the Uniprocessor kernel, even > though SMP problems were supposedly worked around. > (The above steps were taken AFTER coLinux was > installed.) > I disabled McAfee VirusScan before launching > coLinux. > I tried both Gentoo and Debian images. > > During installation, I installed WinPcap 3.1 and > selected the TAP configuration. I disabled windows > firewall on the new connection. I noticed that the > connection icon changes before the machine hangs, > like > it's trying to get an address. > > I would like to get coLinux working, but I don't > know > what else to do. (Although I am getting concerned > about my windows filesystem getting trashed by all > these hangs - good thing it's not FAT). > > > System Info: > Windows XP Professional SP2 > ACPI Multiprocessor kernel > Dual pentium3 1Ghz CPU's > 512M RAM > VP6 VIA Apollo Pro 133A mobo > I have a strange hard disk setup, but I don't think > that's relevant. > > I dual-boot with linux, so the hardware isn't > incompatible with linux or anything like that. I was > not trying to access my existing linux installation > from coLinux at all. > > Config file contents follow. > <?xml version="1.0" encoding="UTF-8"?> > <colinux> > <!-- This line needs to point to your root file > system. > For example change "root_fs" to the name of the > Debian image. > Inside coLinux it will be /dev/cobd0 > > Block Device Aliasing: You can now handle most > dual-boot issues > by adding an alias="devname" to block_device. i.e. > alias="hda", > alias="hda1" You can do this for SCSI as well as > IDE. You need > to be aware that if you add an alias, you need to > change your > bootparams root="devname" appropriately (you may > need to use > devfs naming in some situations). --> > <block_device index="0" > path="\DosDevices\c:\coLinux\Debian-3.0r2.ext3-mit-backports.1gb" > enabled="true" /> > > <!-- This line can specify a swap file if you > wish, or an additional > image file, it will /dev/cobd1. Additional > block_devices can > be specified in the same manner by increasing the > index --> > > <!-- <block_device index="1" > path="\DosDevices\c:\coLinux\swap" enabled="true" /> > --> > > <!-- This is an experimental feature, it may not > function completely. > <cofs_device index="0" type="flat" > path="\DosDevices\C:\" enabled="true" /> > --> > > <!-- bootparams allows you to pass kernel boot > parameters --> > <bootparams>root=/dev/cobd0</bootparams> > > <!-- Initial RamDISK (initrd) support --> > <initrd path="initrd.gz" /> > > <!-- image allows you to specify the kernel to > boot --> > <image path="vmlinux" /> > > <!-- this line allows you to specify the amount > of > memory available > to coLinux --> > <memory size="128" /> > > <!-- This allows you to modify networking > parameters, see the README > or website or wiki for more information --> > <network index="0" type="tap" /> > </colinux> > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam > protection around > http://mail.yahoo.com > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do > you grep through log files > for problems? Stop! Download the new AJAX search > engine that makes > searching your log files as easy as surfing the > web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
From: Holger K. <hol...@gm...> - 2006-02-16 17:43:29
|
<?xml version="1.0" encoding="UTF-8"?> <colinux> <block_device index="0" path="\DosDevices\c:\coLinux\Debian-3.0r2.ext3-mit-backports.1gb" enabled="true" /> <bootparams>root=/dev/cobd0</bootparams> <initrd path="initrd.gz" /> <image path="vmlinux" /> <memory size="128" /> <network index="0" type="tap" /> </colinux> Nothing unusal here. Is colinux stopping or windows? Will readding swap change anything? > I tried both Gentoo and Debian images. > > During installation, I installed WinPcap 3.1 and > selected the TAP configuration. I disabled windows > firewall on the new connection. I noticed that the > connection icon changes before the machine hangs, like > it's trying to get an address. > I would like to get coLinux working, but I don't know > what else to do. (Although I am getting concerned > about my windows filesystem getting trashed by all > these hangs - good thing it's not FAT). Your filesystem will not get trashed. Nothing is written at that moment. (Assuming it is not windows that stops) But i have no idea why colinux stops at that moment, the root filesystem should get mounted. The user that starts colinux is allowd to read/write the image file? |
From: Paul M. <fka...@ya...> - 2006-02-16 17:53:53
|
Windows is stopping, not just colinux. It freezes completely and suddenly- I don't even get a blue screen or any events logged. Originally the swap was pointing to a file (the default), I disabled it in the course of trying to solve the problem. Only thing is, the swap file didn't exist already. Would I have to create it with a tool like dd? In any case, I don't think the coLinux boot sequence even gets to the point that it would try to activate swapping. --- Holger Krull <hol...@gm...> wrote: > <?xml version="1.0" encoding="UTF-8"?> > <colinux> > <block_device index="0" > path="\DosDevices\c:\coLinux\Debian-3.0r2.ext3-mit-backports.1gb" > enabled="true" /> > <bootparams>root=/dev/cobd0</bootparams> > <initrd path="initrd.gz" /> > <image path="vmlinux" /> > <memory size="128" /> > <network index="0" type="tap" /> > </colinux> > > Nothing unusal here. > Is colinux stopping or windows? > Will readding swap change anything? > > > > I tried both Gentoo and Debian images. > > > > During installation, I installed WinPcap 3.1 and > > selected the TAP configuration. I disabled windows > > firewall on the new connection. I noticed that the > > connection icon changes before the machine hangs, > like > > it's trying to get an address. > > > I would like to get coLinux working, but I don't > know > > what else to do. (Although I am getting concerned > > about my windows filesystem getting trashed by all > > these hangs - good thing it's not FAT). > > Your filesystem will not get trashed. Nothing is > written at that moment. (Assuming it is not windows > that stops) > > But i have no idea why colinux stops at that moment, > the root filesystem should get mounted. The user > that starts colinux is allowd to read/write the > image file? > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do > you grep through log files > for problems? Stop! Download the new AJAX search > engine that makes > searching your log files as easy as surfing the > web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
From: Henry N. <Henry.Ne@Arcor.de> - 2006-02-16 17:53:48
|
Paul Mogren wrote: > coLinux is a fantastic idea, and I would love to be > able to use it. This being my first shot at it, I > tried to keep it simple. All I changed from the > default 0.6.3 config is to disable the swap, increase > the memory to "128" and assign the root fs to a > downloaded image. > > Despite that, I can't get very far through the boot > process before the whole machine hangs. The last > message printed before it hangs is "RAMDISK: > Compressed image found at block 0". Comment out the initrd. You not need this for colinux first boots. Only later for some modules. Have you unpacked the file Debian-3.0r2.ext3-mit-backports.1gb and exist this in directory c:\coLinux with 1GB size? Check this with an simple "dir c:\coLinux\Debian-3.0r2.ext3-mit-backports.1gb" on windows command prompt. -- Henry Nestler |
From: Paul M. <fka...@ya...> - 2006-02-16 18:00:21
|
Yes, the debian image is unpacked, the correct size, and in the correct location. I can try without initrd... is it worthwhile to bother with the /noexecute and /NOPAE kernel params and disabling SMP again? --- Henry Nestler <Henry.Ne@Arcor.de> wrote: > Paul Mogren wrote: > > > coLinux is a fantastic idea, and I would love to > be > > able to use it. This being my first shot at it, I > > tried to keep it simple. All I changed from the > > default 0.6.3 config is to disable the swap, > increase > > the memory to "128" and assign the root fs to a > > downloaded image. > > > > Despite that, I can't get very far through the > boot > > process before the whole machine hangs. The last > > message printed before it hangs is "RAMDISK: > > Compressed image found at block 0". > > Comment out the initrd. You not need this for > colinux first boots. > Only later for some modules. > > Have you unpacked the file > Debian-3.0r2.ext3-mit-backports.1gb and exist > this in directory c:\coLinux with 1GB size? Check > this with an simple > "dir c:\coLinux\Debian-3.0r2.ext3-mit-backports.1gb" > on windows command > prompt. > > -- > Henry Nestler > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
From: Paul M. <fka...@ya...> - 2006-02-16 19:09:03
|
--- Henry Nestler <Henry.Ne@Arcor.de> wrote: > Comment out the initrd. You not need this for > colinux first boots. > Only later for some modules. Well, well. I commented out the initrd; it booted. I shutdown coLinux. I uncommented the initrd, and commented out the TAP network instead; it booted. I shutdown coLinux. I uncommented the TAP network, so I'm back to my original config; it booted. All that is with DEP, PAE, SMP, and virus scanner turned on. Sounds good, right? Then I rebooted Windows and tried to launch coLinux again (TAP and initrd enabled)... it hung the machine just like before. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
From: George P B. <geo...@gm...> - 2006-02-17 04:37:28
|
Try creating a batch that does something like this: C:\ CD \coLinux colinux-daemon --remove-driver colinux-daemon --install-driver colinux-daemon -c my-xml.config.xml Does that allow you to boot reliably? On 2/16/06, Paul Mogren <fka...@ya...> wrote: > --- Henry Nestler <Henry.Ne@Arcor.de> wrote: > > Comment out the initrd. You not need this for > > colinux first boots. > > Only later for some modules. > > Well, well. > I commented out the initrd; it booted. > I shutdown coLinux. > I uncommented the initrd, and commented out the TAP > network instead; it booted. > I shutdown coLinux. > I uncommented the TAP network, so I'm back to my > original config; it booted. > All that is with DEP, PAE, SMP, and virus scanner > turned on. Sounds good, right? > Then I rebooted Windows and tried to launch coLinux > again (TAP and initrd enabled)... it hung the machine > just like before. -- George |
From: Paul M. <fka...@ya...> - 2006-02-17 17:53:40
|
George, that did not help. --- George P Boutwell <geo...@gm...> wrote: > Try creating a batch that does something like this: > C:\ > CD \coLinux > colinux-daemon --remove-driver > colinux-daemon --install-driver > colinux-daemon -c my-xml.config.xml > > Does that allow you to boot reliably? > > On 2/16/06, Paul Mogren <fka...@ya...> wrote: > > --- Henry Nestler <Henry.Ne@Arcor.de> wrote: > > > Comment out the initrd. You not need this for > > > colinux first boots. > > > Only later for some modules. > > > > Well, well. > > I commented out the initrd; it booted. > > I shutdown coLinux. > > I uncommented the initrd, and commented out the > TAP > > network instead; it booted. > > I shutdown coLinux. > > I uncommented the TAP network, so I'm back to my > > original config; it booted. > > All that is with DEP, PAE, SMP, and virus scanner > > turned on. Sounds good, right? > > Then I rebooted Windows and tried to launch > coLinux > > again (TAP and initrd enabled)... it hung the > machine > > just like before. > > -- > George > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do > you grep through log files > for problems? Stop! Download the new AJAX search > engine that makes > searching your log files as easy as surfing the > web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
From: Henry N. <Henry.Ne@Arcor.de> - 2006-02-17 12:47:56
|
Paul Mogren schrieb: > --- Henry Nestler <Henry.Ne@Arcor.de> wrote: >> Comment out the initrd. You not need this for >> colinux first boots. >> Only later for some modules. > > Well, well. > I commented out the initrd; it booted. > I shutdown coLinux. > I uncommented the initrd, and commented out the TAP > network instead; it booted. > I shutdown coLinux. > I uncommented the TAP network, so I'm back to my > original config; it booted. > All that is with DEP, PAE, SMP, and virus scanner > turned on. Sounds good, right? > Then I rebooted Windows and tried to launch coLinux > again (TAP and initrd enabled)... it hung the machine > just like before. If you let the initrd disabled for a long while, then runs all times? Also after first start after reboot? PS: The initrd only installs modules. But you have they installed now, and no more need the initrd. You can check it with a ls /lib/modules/linux-2.6.11-co-0.6.3 -- Henry Nestler |
From: Paul M. <fka...@ya...> - 2006-02-17 17:56:11
|
Ok then, I will leave the initrd disabled. It seems to be working in that case, even the first time after reboot. I'll report back if there is anything further to report. Thanks! --- Henry Nestler <Henry.Ne@Arcor.de> wrote: > Paul Mogren schrieb: > > --- Henry Nestler <Henry.Ne@Arcor.de> wrote: > >> Comment out the initrd. You not need this for > >> colinux first boots. > >> Only later for some modules. > > > > Well, well. > > I commented out the initrd; it booted. > > I shutdown coLinux. > > I uncommented the initrd, and commented out the > TAP > > network instead; it booted. > > I shutdown coLinux. > > I uncommented the TAP network, so I'm back to my > > original config; it booted. > > All that is with DEP, PAE, SMP, and virus scanner > > turned on. Sounds good, right? > > Then I rebooted Windows and tried to launch > coLinux > > again (TAP and initrd enabled)... it hung the > machine > > just like before. > > If you let the initrd disabled for a long while, > then runs all times? > Also after first start after reboot? > > PS: The initrd only installs modules. But you have > they installed now, > and no more need the initrd. You can check it with > a > ls /lib/modules/linux-2.6.11-co-0.6.3 > > -- > Henry Nestler > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |