Menu
▾
▴
colinux-users
|
From: Jonathan D. <tz...@sp...> - 2008-06-17 20:00:05
|
I've tried every trick I can find on the web, and I can't get /any/ version of colinux running on Vista SP1. Tried 0.7.3 (release version) and the latest 0.8.x development version. Same exact symptom. What happens is the system boots up, and seems to be just fine. After about 60 seconds, /both /the linux /and/ Vista slow to a crawl and neither is usable. Even if you get Colinux shut down, Vista is /still/ slow as molasses and the only recovery is to reboot (and that's if Vista doesn't freeze on shutdown). Tried with multiple system images (various flavors of Linux), same thing. Tried with the bare Ramdisk boot (just initrd.gz) - same thing. Tried to run a debug on the bare ramdisk boot ... the instant the system started, the entire machine rebooted. No bluescreen, just black screen then POST. So no way to capture debug info, either. So I'm completely stuck ... and this is a huge issue for me ... I do major development work under colinux, and they want to retire my XP box, since the entire company is migrating to Vista. Soon I won't be given a choice; I need this working before that happens ... Anyone got any ideas? Remember ... the image in this case is irrelevant - the problem occurs w/the initrd.gz RAM boot. so it's something endemic to within colinux and its kernel itself. - Jonathan |
|
From: Jonathan D. <tz...@sp...> - 2008-06-17 20:33:06
|
OK ... update ... After diving into the colinux-users archive, I saw a note about the 0.8.0 test version for ntconsoleflood ... that actually seems to have fixed this issue. As noted in the email string that led to that test version, the Vista Business I'm running it on is a multi-core cpu; this may be another example where a SMP setup is breaking the 'older' versions of colinux. My previous system, is a WinXP P4 2.4 .. which is a single cpu system. - Jonathan Jonathan Deitch wrote: > I've tried every trick I can find on the web, and I can't get /any/ > version of colinux running on Vista SP1. > > Tried 0.7.3 (release version) and the latest 0.8.x development > version. Same exact symptom. > > What happens is the system boots up, and seems to be just fine. > > After about 60 seconds, /both /the linux /and/ Vista slow to a crawl > and neither is usable. > > Even if you get Colinux shut down, Vista is /still/ slow as molasses > and the only recovery is to reboot (and that's if Vista doesn't freeze > on shutdown). > > Tried with multiple system images (various flavors of Linux), same thing. > > Tried with the bare Ramdisk boot (just initrd.gz) - same thing. > > Tried to run a debug on the bare ramdisk boot ... the instant the > system started, the entire machine rebooted. No bluescreen, just > black screen then POST. > > So no way to capture debug info, either. > > So I'm completely stuck ... and this is a huge issue for me ... I do > major development work under colinux, and they want to retire my XP > box, since the entire company is migrating to Vista. > > Soon I won't be given a choice; I need this working before that > happens ... > > Anyone got any ideas? > > Remember ... the image in this case is irrelevant - the problem occurs > w/the initrd.gz RAM boot. so it's something endemic to within colinux > and its kernel itself. > > - Jonathan > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > ------------------------------------------------------------------------ > > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
|
From: Jonathan D. <tz...@sp...> - 2008-06-17 20:32:00
|
Whoops ... I spoke too soon. The "ntconsoleflood" 0.8.0 version allows the system to boot, and run for a bit. After about 5 minutes, however, the same exact circumstances as before occur. Reproduced with all the same settings (including the barebones /dev/RAM boot). Same symptoms with vista before after colinux shutdown - everything runs very slow, entire PC is unusable. So still no solution. - Jonathan Jonathan Deitch wrote: > OK ... update ... > > After diving into the colinux-users archive, I saw a note about the > 0.8.0 test version for ntconsoleflood ... that actually seems to have > fixed this issue. > > As noted in the email string that led to that test version, the Vista > Business I'm running it on is a multi-core cpu; this may be another > example where a SMP setup is breaking the 'older' versions of colinux. > > My previous system, is a WinXP P4 2.4 .. which is a single cpu system. > > - Jonathan > > Jonathan Deitch wrote: >> I've tried every trick I can find on the web, and I can't get /any/ >> version of colinux running on Vista SP1. >> >> Tried 0.7.3 (release version) and the latest 0.8.x development >> version. Same exact symptom. >> >> What happens is the system boots up, and seems to be just fine. >> >> After about 60 seconds, /both /the linux /and/ Vista slow to a crawl >> and neither is usable. >> >> Even if you get Colinux shut down, Vista is /still/ slow as molasses >> and the only recovery is to reboot (and that's if Vista doesn't >> freeze on shutdown). >> >> Tried with multiple system images (various flavors of Linux), same thing. >> >> Tried with the bare Ramdisk boot (just initrd.gz) - same thing. >> >> Tried to run a debug on the bare ramdisk boot ... the instant the >> system started, the entire machine rebooted. No bluescreen, just >> black screen then POST. >> >> So no way to capture debug info, either. >> >> So I'm completely stuck ... and this is a huge issue for me ... I do >> major development work under colinux, and they want to retire my XP >> box, since the entire company is migrating to Vista. >> >> Soon I won't be given a choice; I need this working before that >> happens ... >> >> Anyone got any ideas? >> >> Remember ... the image in this case is irrelevant - the problem >> occurs w/the initrd.gz RAM boot. so it's something endemic to within >> colinux and its kernel itself. >> >> - Jonathan >> ------------------------------------------------------------------------ >> >> ------------------------------------------------------------------------- >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source. >> http://sourceforge.net/services/buy/index.php >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> coLinux-users mailing list >> coL...@li... >> https://lists.sourceforge.net/lists/listinfo/colinux-users >> |
|
From: Henry N. <hen...@ar...> - 2008-06-18 00:50:58
|
I have no Vista running. But from an example of install I have lots of screenshots. Perhaps you will find suggestions from there: http://www.henrynestler.com/colinux/screenshoots/Vista-Album The "ntconsoleflood" is also fixed in coLinux version 0.7.3 final release. Henry Jonathan Deitch wrote: > Whoops ... I spoke too soon. > > The "ntconsoleflood" 0.8.0 version allows the system to boot, and run > for a bit. > > After about 5 minutes, however, the same exact circumstances as before > occur. > > Reproduced with all the same settings (including the barebones /dev/RAM > boot). > > Same symptoms with vista before after colinux shutdown - everything runs > very slow, entire PC is unusable. > > So still no solution. > > - Jonathan > > Jonathan Deitch wrote: >> OK ... update ... >> >> After diving into the colinux-users archive, I saw a note about the >> 0.8.0 test version for ntconsoleflood ... that actually seems to have >> fixed this issue. >> >> As noted in the email string that led to that test version, the Vista >> Business I'm running it on is a multi-core cpu; this may be another >> example where a SMP setup is breaking the 'older' versions of colinux. >> >> My previous system, is a WinXP P4 2.4 .. which is a single cpu system. >> >> - Jonathan >> >> Jonathan Deitch wrote: >>> I've tried every trick I can find on the web, and I can't get /any/ >>> version of colinux running on Vista SP1. >>> >>> Tried 0.7.3 (release version) and the latest 0.8.x development >>> version. Same exact symptom. >>> >>> What happens is the system boots up, and seems to be just fine. >>> >>> After about 60 seconds, /both /the linux /and/ Vista slow to a crawl >>> and neither is usable. >>> >>> Even if you get Colinux shut down, Vista is /still/ slow as molasses >>> and the only recovery is to reboot (and that's if Vista doesn't >>> freeze on shutdown). >>> >>> Tried with multiple system images (various flavors of Linux), same thing. >>> >>> Tried with the bare Ramdisk boot (just initrd.gz) - same thing. >>> >>> Tried to run a debug on the bare ramdisk boot ... the instant the >>> system started, the entire machine rebooted. No bluescreen, just >>> black screen then POST. >>> >>> So no way to capture debug info, either. >>> >>> So I'm completely stuck ... and this is a huge issue for me ... I do >>> major development work under colinux, and they want to retire my XP >>> box, since the entire company is migrating to Vista. >>> >>> Soon I won't be given a choice; I need this working before that >>> happens ... >>> >>> Anyone got any ideas? >>> >>> Remember ... the image in this case is irrelevant - the problem >>> occurs w/the initrd.gz RAM boot. so it's something endemic to within >>> colinux and its kernel itself. >>> >>> - Jonathan >>> >>> ------------------------------------------------------------------------- >>> Check out the new SourceForge.net Marketplace. >>> It's the best place to buy or sell services for >>> just about anything Open Source. >>> http://sourceforge.net/services/buy/index.php >>> >>> _______________________________________________ >>> coLinux-users mailing list >>> coL...@li... <mailto:coL...@li...> >>> https://lists.sourceforge.net/lists/listinfo/colinux-users >>> > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > > > ------------------------------------------------------------------------ |
|
From: Jonathan D. <tz...@sp...> - 2008-06-18 00:59:12
|
I saw a definite difference in behavior between the 0.7.3 and the "ntflood" 0.8.0 ... 0.7.3 would cause the system to lockup within a minute ... 0.8.0 ntflood would run OK for 4-5 minutes and then lock up (same exact symptoms). The pictures, unfortunately, do not help. As I memtioned, this problem occurs with minimal settings (initrd and root) booting the initrd ram boot. No image, no network, no nothing. If I can't get the RAM boot to work, then there's no point going any farther with anything else. Any ideas? I really need help on this ... if there isn't a solution soon, I will probably be forced to abandon using colinux altogether, and rethinking my whole way of working. :-( - Jonathan Henry Nestler wrote: > I have no Vista running. But from an example of install I have lots of > screenshots. Perhaps you will find suggestions from there: > http://www.henrynestler.com/colinux/screenshoots/Vista-Album > > The "ntconsoleflood" is also fixed in coLinux version 0.7.3 final release. > > Henry > > Jonathan Deitch wrote: > >> Whoops ... I spoke too soon. >> >> The "ntconsoleflood" 0.8.0 version allows the system to boot, and run >> for a bit. >> >> After about 5 minutes, however, the same exact circumstances as before >> occur. >> >> Reproduced with all the same settings (including the barebones /dev/RAM >> boot). >> >> Same symptoms with vista before after colinux shutdown - everything runs >> very slow, entire PC is unusable. >> >> So still no solution. >> >> - Jonathan >> >> Jonathan Deitch wrote: >> >>> OK ... update ... >>> >>> After diving into the colinux-users archive, I saw a note about the >>> 0.8.0 test version for ntconsoleflood ... that actually seems to have >>> fixed this issue. >>> >>> As noted in the email string that led to that test version, the Vista >>> Business I'm running it on is a multi-core cpu; this may be another >>> example where a SMP setup is breaking the 'older' versions of colinux. >>> >>> My previous system, is a WinXP P4 2.4 .. which is a single cpu system. >>> >>> - Jonathan >>> >>> Jonathan Deitch wrote: >>> >>>> I've tried every trick I can find on the web, and I can't get /any/ >>>> version of colinux running on Vista SP1. >>>> >>>> Tried 0.7.3 (release version) and the latest 0.8.x development >>>> version. Same exact symptom. >>>> >>>> What happens is the system boots up, and seems to be just fine. >>>> >>>> After about 60 seconds, /both /the linux /and/ Vista slow to a crawl >>>> and neither is usable. >>>> >>>> Even if you get Colinux shut down, Vista is /still/ slow as molasses >>>> and the only recovery is to reboot (and that's if Vista doesn't >>>> freeze on shutdown). >>>> >>>> Tried with multiple system images (various flavors of Linux), same thing. >>>> >>>> Tried with the bare Ramdisk boot (just initrd.gz) - same thing. >>>> >>>> Tried to run a debug on the bare ramdisk boot ... the instant the >>>> system started, the entire machine rebooted. No bluescreen, just >>>> black screen then POST. >>>> >>>> So no way to capture debug info, either. >>>> >>>> So I'm completely stuck ... and this is a huge issue for me ... I do >>>> major development work under colinux, and they want to retire my XP >>>> box, since the entire company is migrating to Vista. >>>> >>>> Soon I won't be given a choice; I need this working before that >>>> happens ... >>>> >>>> Anyone got any ideas? >>>> >>>> Remember ... the image in this case is irrelevant - the problem >>>> occurs w/the initrd.gz RAM boot. so it's something endemic to within >>>> colinux and its kernel itself. >>>> >>>> - Jonathan >>>> >>>> ------------------------------------------------------------------------- >>>> Check out the new SourceForge.net Marketplace. >>>> It's the best place to buy or sell services for >>>> just about anything Open Source. >>>> http://sourceforge.net/services/buy/index.php >>>> >>>> _______________________________________________ >>>> coLinux-users mailing list >>>> coL...@li... <mailto:coL...@li...> >>>> https://lists.sourceforge.net/lists/listinfo/colinux-users >>>> >>>> >> ------------------------------------------------------------------------ >> >> ------------------------------------------------------------------------- >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source. >> http://sourceforge.net/services/buy/index.php >> >> >> ------------------------------------------------------------------------ >> |
|
From: Paolo M. <pao...@gm...> - 2008-06-18 07:31:51
|
At home I have Vista. I have used a little colinux on Vista, only to see if it works. I had found the bug of "flooding", that Henry have solved. The other things seem work for me .... I don't have important problem. But I use it a little. I use a lot colinux on XP at work. It is interesting understand what exactly works and what has problems.... Have you problem with a very simple ramdisk ? I could try your images .... Bye, Paolo On Wed, Jun 18, 2008 at 2:58 AM, Jonathan Deitch <tz...@sp...> wrote: > I saw a definite difference in behavior between the 0.7.3 and the > "ntflood" 0.8.0 ... > > 0.7.3 would cause the system to lockup within a minute ... 0.8.0 ntflood > would run OK for 4-5 minutes and then lock up (same exact symptoms). > > The pictures, unfortunately, do not help. > > As I memtioned, this problem occurs with minimal settings (initrd and > root) booting the initrd ram boot. > > No image, no network, no nothing. > > If I can't get the RAM boot to work, then there's no point going any > farther with anything else. > > Any ideas? I really need help on this ... if there isn't a solution > soon, I will probably be forced to abandon using colinux altogether, and > rethinking my whole way of working. :-( > > - Jonathan > Henry Nestler wrote: >> I have no Vista running. But from an example of install I have lots of >> screenshots. Perhaps you will find suggestions from there: >> http://www.henrynestler.com/colinux/screenshoots/Vista-Album >> >> The "ntconsoleflood" is also fixed in coLinux version 0.7.3 final release. >> >> Henry >> >> Jonathan Deitch wrote: >> >>> Whoops ... I spoke too soon. >>> >>> The "ntconsoleflood" 0.8.0 version allows the system to boot, and run >>> for a bit. >>> >>> After about 5 minutes, however, the same exact circumstances as before >>> occur. >>> >>> Reproduced with all the same settings (including the barebones /dev/RAM >>> boot). >>> >>> Same symptoms with vista before after colinux shutdown - everything runs >>> very slow, entire PC is unusable. >>> >>> So still no solution. >>> >>> - Jonathan >>> >>> Jonathan Deitch wrote: >>> >>>> OK ... update ... >>>> >>>> After diving into the colinux-users archive, I saw a note about the >>>> 0.8.0 test version for ntconsoleflood ... that actually seems to have >>>> fixed this issue. >>>> >>>> As noted in the email string that led to that test version, the Vista >>>> Business I'm running it on is a multi-core cpu; this may be another >>>> example where a SMP setup is breaking the 'older' versions of colinux. >>>> >>>> My previous system, is a WinXP P4 2.4 .. which is a single cpu system. >>>> >>>> - Jonathan >>>> >>>> Jonathan Deitch wrote: >>>> >>>>> I've tried every trick I can find on the web, and I can't get /any/ >>>>> version of colinux running on Vista SP1. >>>>> >>>>> Tried 0.7.3 (release version) and the latest 0.8.x development >>>>> version. Same exact symptom. >>>>> >>>>> What happens is the system boots up, and seems to be just fine. >>>>> >>>>> After about 60 seconds, /both /the linux /and/ Vista slow to a crawl >>>>> and neither is usable. >>>>> >>>>> Even if you get Colinux shut down, Vista is /still/ slow as molasses >>>>> and the only recovery is to reboot (and that's if Vista doesn't >>>>> freeze on shutdown). >>>>> >>>>> Tried with multiple system images (various flavors of Linux), same thing. >>>>> >>>>> Tried with the bare Ramdisk boot (just initrd.gz) - same thing. >>>>> >>>>> Tried to run a debug on the bare ramdisk boot ... the instant the >>>>> system started, the entire machine rebooted. No bluescreen, just >>>>> black screen then POST. >>>>> >>>>> So no way to capture debug info, either. >>>>> >>>>> So I'm completely stuck ... and this is a huge issue for me ... I do >>>>> major development work under colinux, and they want to retire my XP >>>>> box, since the entire company is migrating to Vista. >>>>> >>>>> Soon I won't be given a choice; I need this working before that >>>>> happens ... >>>>> >>>>> Anyone got any ideas? >>>>> >>>>> Remember ... the image in this case is irrelevant - the problem >>>>> occurs w/the initrd.gz RAM boot. so it's something endemic to within >>>>> colinux and its kernel itself. >>>>> >>>>> - Jonathan >>>>> >>>>> ------------------------------------------------------------------------- >>>>> Check out the new SourceForge.net Marketplace. >>>>> It's the best place to buy or sell services for >>>>> just about anything Open Source. >>>>> http://sourceforge.net/services/buy/index.php >>>>> >>>>> _______________________________________________ >>>>> coLinux-users mailing list >>>>> coL...@li... <mailto:coL...@li...> >>>>> https://lists.sourceforge.net/lists/listinfo/colinux-users >>>>> >>>>> >>> ------------------------------------------------------------------------ >>> >>> ------------------------------------------------------------------------- >>> Check out the new SourceForge.net Marketplace. >>> It's the best place to buy or sell services for >>> just about anything Open Source. >>> http://sourceforge.net/services/buy/index.php >>> >>> >>> ------------------------------------------------------------------------ >>> > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
|
From: Jonathan D. <tz...@sp...> - 2008-06-18 15:30:50
|
I have the problem with the simple ramdisk (so no images) no matter what version I try. The only difference is, with the "ntflood" 0.8.0 version, the onset of the slow response is delayed several minutes. When the 'slow response' problem occurs, it affects BOTH colinux and windows, and continues to affect windows even after colinux is shut down. The only way to recover is to reboot. - Jonathan Paolo Minazzi wrote: > At home I have Vista. > I have used a little colinux on Vista, only to see if it works. > I had found the bug of "flooding", that Henry have solved. > The other things seem work for me .... I don't have important problem. > But I use it a little. I use a lot colinux on XP at work. > It is interesting understand what exactly works and what has problems.... > Have you problem with a very simple ramdisk ? > I could try your images .... > Bye, > Paolo > > On Wed, Jun 18, 2008 at 2:58 AM, Jonathan Deitch <tz...@sp...> wrote: > >> I saw a definite difference in behavior between the 0.7.3 and the >> "ntflood" 0.8.0 ... >> >> 0.7.3 would cause the system to lockup within a minute ... 0.8.0 ntflood >> would run OK for 4-5 minutes and then lock up (same exact symptoms). >> >> The pictures, unfortunately, do not help. >> >> As I memtioned, this problem occurs with minimal settings (initrd and >> root) booting the initrd ram boot. >> >> No image, no network, no nothing. >> >> If I can't get the RAM boot to work, then there's no point going any >> farther with anything else. >> >> Any ideas? I really need help on this ... if there isn't a solution >> soon, I will probably be forced to abandon using colinux altogether, and >> rethinking my whole way of working. :-( >> >> - Jonathan >> Henry Nestler wrote: >> >>> I have no Vista running. But from an example of install I have lots of >>> screenshots. Perhaps you will find suggestions from there: >>> http://www.henrynestler.com/colinux/screenshoots/Vista-Album >>> >>> The "ntconsoleflood" is also fixed in coLinux version 0.7.3 final release. >>> >>> Henry >>> >>> Jonathan Deitch wrote: >>> >>> >>>> Whoops ... I spoke too soon. >>>> >>>> The "ntconsoleflood" 0.8.0 version allows the system to boot, and run >>>> for a bit. >>>> >>>> After about 5 minutes, however, the same exact circumstances as before >>>> occur. >>>> >>>> Reproduced with all the same settings (including the barebones /dev/RAM >>>> boot). >>>> >>>> Same symptoms with vista before after colinux shutdown - everything runs >>>> very slow, entire PC is unusable. >>>> >>>> So still no solution. >>>> >>>> - Jonathan >>>> >>>> Jonathan Deitch wrote: >>>> >>>> >>>>> OK ... update ... >>>>> >>>>> After diving into the colinux-users archive, I saw a note about the >>>>> 0.8.0 test version for ntconsoleflood ... that actually seems to have >>>>> fixed this issue. >>>>> >>>>> As noted in the email string that led to that test version, the Vista >>>>> Business I'm running it on is a multi-core cpu; this may be another >>>>> example where a SMP setup is breaking the 'older' versions of colinux. >>>>> >>>>> My previous system, is a WinXP P4 2.4 .. which is a single cpu system. >>>>> >>>>> - Jonathan >>>>> >>>>> Jonathan Deitch wrote: >>>>> >>>>> >>>>>> I've tried every trick I can find on the web, and I can't get /any/ >>>>>> version of colinux running on Vista SP1. >>>>>> >>>>>> Tried 0.7.3 (release version) and the latest 0.8.x development >>>>>> version. Same exact symptom. >>>>>> >>>>>> What happens is the system boots up, and seems to be just fine. >>>>>> >>>>>> After about 60 seconds, /both /the linux /and/ Vista slow to a crawl >>>>>> and neither is usable. >>>>>> >>>>>> Even if you get Colinux shut down, Vista is /still/ slow as molasses >>>>>> and the only recovery is to reboot (and that's if Vista doesn't >>>>>> freeze on shutdown). >>>>>> >>>>>> Tried with multiple system images (various flavors of Linux), same thing. >>>>>> >>>>>> Tried with the bare Ramdisk boot (just initrd.gz) - same thing. >>>>>> >>>>>> Tried to run a debug on the bare ramdisk boot ... the instant the >>>>>> system started, the entire machine rebooted. No bluescreen, just >>>>>> black screen then POST. >>>>>> >>>>>> So no way to capture debug info, either. >>>>>> >>>>>> So I'm completely stuck ... and this is a huge issue for me ... I do >>>>>> major development work under colinux, and they want to retire my XP >>>>>> box, since the entire company is migrating to Vista. >>>>>> >>>>>> Soon I won't be given a choice; I need this working before that >>>>>> happens ... >>>>>> >>>>>> Anyone got any ideas? >>>>>> >>>>>> Remember ... the image in this case is irrelevant - the problem >>>>>> occurs w/the initrd.gz RAM boot. so it's something endemic to within >>>>>> colinux and its kernel itself. >>>>>> >>>>>> - Jonathan >>>>>> >>>>>> ------------------------------------------------------------------------- >>>>>> Check out the new SourceForge.net Marketplace. >>>>>> It's the best place to buy or sell services for >>>>>> just about anything Open Source. >>>>>> http://sourceforge.net/services/buy/index.php >>>>>> >>>>>> _______________________________________________ >>>>>> coLinux-users mailing list >>>>>> coL...@li... <mailto:coL...@li...> >>>>>> https://lists.sourceforge.net/lists/listinfo/colinux-users >>>>>> >>>>>> >>>>>> >>>> ------------------------------------------------------------------------ >>>> >>>> ------------------------------------------------------------------------- >>>> Check out the new SourceForge.net Marketplace. >>>> It's the best place to buy or sell services for >>>> just about anything Open Source. >>>> http://sourceforge.net/services/buy/index.php >>>> >>>> >>>> ------------------------------------------------------------------------ >>>> >>>> >> ------------------------------------------------------------------------- >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source. >> http://sourceforge.net/services/buy/index.php >> _______________________________________________ >> coLinux-users mailing list >> coL...@li... >> https://lists.sourceforge.net/lists/listinfo/colinux-users >> >> > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
|
From: Josep M. A. S. <ja...@pa...> - 2008-06-18 17:07:36
|
May I ask some more information about the System?
Here i am running Vista Home Premium SP1 (Spanish) with colinux 0.7.3, on a core
2 duo laptop (centrino duo) with 2GB of RAM.
The amount of RAM for colinux is 256MB.
The only problem i had with it was with some random reboots, which in my case,
were due to the problems with ext2 and ext3 fixed recently.
my config file is as follows:
kernel=vmlinux
#reenable each time colinux daemon is updated, so that modules can be updated
aswell.
initrd=initrd.gz
cobd0=D:\Colinux\debian\Debian-etch.ext3.3gb
cobd3=D:\Colinux\debian\swap_128Mb
cofs0=C:\
cofs1=D:\
mem=256
eth0=tuntap
#eth1=pcap-bridge,ethernet
root=/dev/cobd0
Note that I run it as a service, but i've tried running it manually with the
following script with no problems:
c:
cd "c:\Program Files\colinux\"
start colinux-daemon.exe -t nt @D:\Colinux\debian\debian.colinux.conf.txt
start colinux-console-nt.exe
--
_ _ /~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-\
o o | Josep Ma [JAZ] |
* | ICQ UIN: 7014661 |
`-´ | Messenger: ja...@ho... |
\-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~/
|
|
From: Steve W. <li...@la...> - 2008-06-18 07:33:23
|
I cant help you, but i can say that "Linux colinux 2.6.17-co-0.8.0 #2" works with Vista SP1 on an Core Duo without any problem for me. Steve Jonathan Deitch schrieb: > I saw a definite difference in behavior between the 0.7.3 and the > "ntflood" 0.8.0 ... > > 0.7.3 would cause the system to lockup within a minute ... 0.8.0 ntflood > would run OK for 4-5 minutes and then lock up (same exact symptoms). > > The pictures, unfortunately, do not help. > > As I memtioned, this problem occurs with minimal settings (initrd and > root) booting the initrd ram boot. > > No image, no network, no nothing. > > If I can't get the RAM boot to work, then there's no point going any > farther with anything else. > > Any ideas? I really need help on this ... if there isn't a solution > soon, I will probably be forced to abandon using colinux altogether, and > rethinking my whole way of working. :-( > > - Jonathan > Henry Nestler wrote: >> I have no Vista running. But from an example of install I have lots of >> screenshots. Perhaps you will find suggestions from there: >> http://www.henrynestler.com/colinux/screenshoots/Vista-Album >> >> The "ntconsoleflood" is also fixed in coLinux version 0.7.3 final release. >> >> Henry >> >> Jonathan Deitch wrote: >> >>> Whoops ... I spoke too soon. >>> >>> The "ntconsoleflood" 0.8.0 version allows the system to boot, and run >>> for a bit. >>> >>> After about 5 minutes, however, the same exact circumstances as before >>> occur. >>> >>> Reproduced with all the same settings (including the barebones /dev/RAM >>> boot). >>> >>> Same symptoms with vista before after colinux shutdown - everything runs >>> very slow, entire PC is unusable. >>> >>> So still no solution. >>> >>> - Jonathan >>> >>> Jonathan Deitch wrote: >>> >>>> OK ... update ... >>>> >>>> After diving into the colinux-users archive, I saw a note about the >>>> 0.8.0 test version for ntconsoleflood ... that actually seems to have >>>> fixed this issue. >>>> >>>> As noted in the email string that led to that test version, the Vista >>>> Business I'm running it on is a multi-core cpu; this may be another >>>> example where a SMP setup is breaking the 'older' versions of colinux. >>>> >>>> My previous system, is a WinXP P4 2.4 .. which is a single cpu system. >>>> >>>> - Jonathan >>>> >>>> Jonathan Deitch wrote: >>>> >>>>> I've tried every trick I can find on the web, and I can't get /any/ >>>>> version of colinux running on Vista SP1. >>>>> >>>>> Tried 0.7.3 (release version) and the latest 0.8.x development >>>>> version. Same exact symptom. >>>>> >>>>> What happens is the system boots up, and seems to be just fine. >>>>> >>>>> After about 60 seconds, /both /the linux /and/ Vista slow to a crawl >>>>> and neither is usable. >>>>> >>>>> Even if you get Colinux shut down, Vista is /still/ slow as molasses >>>>> and the only recovery is to reboot (and that's if Vista doesn't >>>>> freeze on shutdown). >>>>> >>>>> Tried with multiple system images (various flavors of Linux), same thing. >>>>> >>>>> Tried with the bare Ramdisk boot (just initrd.gz) - same thing. >>>>> >>>>> Tried to run a debug on the bare ramdisk boot ... the instant the >>>>> system started, the entire machine rebooted. No bluescreen, just >>>>> black screen then POST. >>>>> >>>>> So no way to capture debug info, either. >>>>> >>>>> So I'm completely stuck ... and this is a huge issue for me ... I do >>>>> major development work under colinux, and they want to retire my XP >>>>> box, since the entire company is migrating to Vista. >>>>> >>>>> Soon I won't be given a choice; I need this working before that >>>>> happens ... >>>>> >>>>> Anyone got any ideas? >>>>> >>>>> Remember ... the image in this case is irrelevant - the problem >>>>> occurs w/the initrd.gz RAM boot. so it's something endemic to within >>>>> colinux and its kernel itself. >>>>> >>>>> - Jonathan >>>>> >>>>> ------------------------------------------------------------------------- >>>>> Check out the new SourceForge.net Marketplace. >>>>> It's the best place to buy or sell services for >>>>> just about anything Open Source. >>>>> http://sourceforge.net/services/buy/index.php >>>>> >>>>> _______________________________________________ >>>>> coLinux-users mailing list >>>>> coL...@li... <mailto:coL...@li...> >>>>> https://lists.sourceforge.net/lists/listinfo/colinux-users >>>>> >>>>> >>> ------------------------------------------------------------------------ >>> >>> ------------------------------------------------------------------------- >>> Check out the new SourceForge.net Marketplace. >>> It's the best place to buy or sell services for >>> just about anything Open Source. >>> http://sourceforge.net/services/buy/index.php >>> >>> >>> ------------------------------------------------------------------------ >>> > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
|
From: Steve W. <li...@la...> - 2008-06-18 08:04:07
|
No i used a development snapshot downloaded from colinux.org. Steve Henry Nestler schrieb: > Hello Steve, > > thank you for your post. > > You have self compiled the kernel? Please let us see your used gcc and > type inside: "dmesg | head -n1" > > Please send me your kernel config. > > Henry > > Steve Wagner wrote: >> I cant help you, but i can say that "Linux colinux 2.6.17-co-0.8.0 #2" >> works with Vista SP1 on an Core Duo without any problem for me. >> >> Steve >> >> Jonathan Deitch schrieb: >>> I saw a definite difference in behavior between the 0.7.3 and the >>> "ntflood" 0.8.0 ... >>> >>> 0.7.3 would cause the system to lockup within a minute ... 0.8.0 ntflood >>> would run OK for 4-5 minutes and then lock up (same exact symptoms). >>> >>> The pictures, unfortunately, do not help. >>> >>> As I memtioned, this problem occurs with minimal settings (initrd and >>> root) booting the initrd ram boot. >>> >>> No image, no network, no nothing. >>> >>> If I can't get the RAM boot to work, then there's no point going any >>> farther with anything else. >>> >>> Any ideas? I really need help on this ... if there isn't a solution >>> soon, I will probably be forced to abandon using colinux altogether, and >>> rethinking my whole way of working. :-( >>> >>> - Jonathan >>> Henry Nestler wrote: >>>> I have no Vista running. But from an example of install I have lots of >>>> screenshots. Perhaps you will find suggestions from there: >>>> http://www.henrynestler.com/colinux/screenshoots/Vista-Album >>>> >>>> The "ntconsoleflood" is also fixed in coLinux version 0.7.3 final release. >>>> >>>> Henry >>>> >>>> Jonathan Deitch wrote: >>>> >>>>> Whoops ... I spoke too soon. >>>>> >>>>> The "ntconsoleflood" 0.8.0 version allows the system to boot, and run >>>>> for a bit. >>>>> >>>>> After about 5 minutes, however, the same exact circumstances as before >>>>> occur. >>>>> >>>>> Reproduced with all the same settings (including the barebones /dev/RAM >>>>> boot). >>>>> >>>>> Same symptoms with vista before after colinux shutdown - everything runs >>>>> very slow, entire PC is unusable. >>>>> >>>>> So still no solution. >>>>> >>>>> - Jonathan >>>>> >>>>> Jonathan Deitch wrote: >>>>> >>>>>> OK ... update ... >>>>>> >>>>>> After diving into the colinux-users archive, I saw a note about the >>>>>> 0.8.0 test version for ntconsoleflood ... that actually seems to have >>>>>> fixed this issue. >>>>>> >>>>>> As noted in the email string that led to that test version, the Vista >>>>>> Business I'm running it on is a multi-core cpu; this may be another >>>>>> example where a SMP setup is breaking the 'older' versions of colinux. >>>>>> >>>>>> My previous system, is a WinXP P4 2.4 .. which is a single cpu system. >>>>>> >>>>>> - Jonathan >>>>>> >>>>>> Jonathan Deitch wrote: >>>>>> >>>>>>> I've tried every trick I can find on the web, and I can't get /any/ >>>>>>> version of colinux running on Vista SP1. >>>>>>> >>>>>>> Tried 0.7.3 (release version) and the latest 0.8.x development >>>>>>> version. Same exact symptom. >>>>>>> >>>>>>> What happens is the system boots up, and seems to be just fine. >>>>>>> >>>>>>> After about 60 seconds, /both /the linux /and/ Vista slow to a crawl >>>>>>> and neither is usable. >>>>>>> >>>>>>> Even if you get Colinux shut down, Vista is /still/ slow as molasses >>>>>>> and the only recovery is to reboot (and that's if Vista doesn't >>>>>>> freeze on shutdown). >>>>>>> >>>>>>> Tried with multiple system images (various flavors of Linux), same thing. >>>>>>> >>>>>>> Tried with the bare Ramdisk boot (just initrd.gz) - same thing. >>>>>>> >>>>>>> Tried to run a debug on the bare ramdisk boot ... the instant the >>>>>>> system started, the entire machine rebooted. No bluescreen, just >>>>>>> black screen then POST. >>>>>>> >>>>>>> So no way to capture debug info, either. >>>>>>> >>>>>>> So I'm completely stuck ... and this is a huge issue for me ... I do >>>>>>> major development work under colinux, and they want to retire my XP >>>>>>> box, since the entire company is migrating to Vista. >>>>>>> >>>>>>> Soon I won't be given a choice; I need this working before that >>>>>>> happens ... >>>>>>> >>>>>>> Anyone got any ideas? >>>>>>> >>>>>>> Remember ... the image in this case is irrelevant - the problem >>>>>>> occurs w/the initrd.gz RAM boot. so it's something endemic to within >>>>>>> colinux and its kernel itself. >>>>>>> >>>>>>> - Jonathan >>>>>>> >>>>>>> ------------------------------------------------------------------------- > |
|
From: Steve W. <li...@la...> - 2008-06-18 09:51:14
|
Ive know upgraded to lastest stable "Linux colinux 2.6.22.18-co-0.7.3 #1" coLinux-stable-20080524 and it also works fine. Steve Steve Wagner schrieb: > No i used a development snapshot downloaded from colinux.org. > > Steve > > Henry Nestler schrieb: >> Hello Steve, >> >> thank you for your post. >> >> You have self compiled the kernel? Please let us see your used gcc and >> type inside: "dmesg | head -n1" >> >> Please send me your kernel config. >> >> Henry >> >> Steve Wagner wrote: >>> I cant help you, but i can say that "Linux colinux 2.6.17-co-0.8.0 #2" >>> works with Vista SP1 on an Core Duo without any problem for me. >>> >>> Steve >>> >>> Jonathan Deitch schrieb: >>>> I saw a definite difference in behavior between the 0.7.3 and the >>>> "ntflood" 0.8.0 ... >>>> >>>> 0.7.3 would cause the system to lockup within a minute ... 0.8.0 ntflood >>>> would run OK for 4-5 minutes and then lock up (same exact symptoms). >>>> >>>> The pictures, unfortunately, do not help. >>>> >>>> As I memtioned, this problem occurs with minimal settings (initrd and >>>> root) booting the initrd ram boot. >>>> >>>> No image, no network, no nothing. >>>> >>>> If I can't get the RAM boot to work, then there's no point going any >>>> farther with anything else. >>>> >>>> Any ideas? I really need help on this ... if there isn't a solution >>>> soon, I will probably be forced to abandon using colinux altogether, and >>>> rethinking my whole way of working. :-( >>>> >>>> - Jonathan >>>> Henry Nestler wrote: >>>>> I have no Vista running. But from an example of install I have lots of >>>>> screenshots. Perhaps you will find suggestions from there: >>>>> http://www.henrynestler.com/colinux/screenshoots/Vista-Album >>>>> >>>>> The "ntconsoleflood" is also fixed in coLinux version 0.7.3 final release. >>>>> >>>>> Henry >>>>> >>>>> Jonathan Deitch wrote: >>>>> >>>>>> Whoops ... I spoke too soon. >>>>>> >>>>>> The "ntconsoleflood" 0.8.0 version allows the system to boot, and run >>>>>> for a bit. >>>>>> >>>>>> After about 5 minutes, however, the same exact circumstances as before >>>>>> occur. >>>>>> >>>>>> Reproduced with all the same settings (including the barebones /dev/RAM >>>>>> boot). >>>>>> >>>>>> Same symptoms with vista before after colinux shutdown - everything runs >>>>>> very slow, entire PC is unusable. >>>>>> >>>>>> So still no solution. >>>>>> >>>>>> - Jonathan >>>>>> >>>>>> Jonathan Deitch wrote: >>>>>> >>>>>>> OK ... update ... >>>>>>> >>>>>>> After diving into the colinux-users archive, I saw a note about the >>>>>>> 0.8.0 test version for ntconsoleflood ... that actually seems to have >>>>>>> fixed this issue. >>>>>>> >>>>>>> As noted in the email string that led to that test version, the Vista >>>>>>> Business I'm running it on is a multi-core cpu; this may be another >>>>>>> example where a SMP setup is breaking the 'older' versions of colinux. >>>>>>> >>>>>>> My previous system, is a WinXP P4 2.4 .. which is a single cpu system. >>>>>>> >>>>>>> - Jonathan >>>>>>> >>>>>>> Jonathan Deitch wrote: >>>>>>> >>>>>>>> I've tried every trick I can find on the web, and I can't get /any/ >>>>>>>> version of colinux running on Vista SP1. >>>>>>>> >>>>>>>> Tried 0.7.3 (release version) and the latest 0.8.x development >>>>>>>> version. Same exact symptom. >>>>>>>> >>>>>>>> What happens is the system boots up, and seems to be just fine. >>>>>>>> >>>>>>>> After about 60 seconds, /both /the linux /and/ Vista slow to a crawl >>>>>>>> and neither is usable. >>>>>>>> >>>>>>>> Even if you get Colinux shut down, Vista is /still/ slow as molasses >>>>>>>> and the only recovery is to reboot (and that's if Vista doesn't >>>>>>>> freeze on shutdown). >>>>>>>> >>>>>>>> Tried with multiple system images (various flavors of Linux), same thing. >>>>>>>> >>>>>>>> Tried with the bare Ramdisk boot (just initrd.gz) - same thing. >>>>>>>> >>>>>>>> Tried to run a debug on the bare ramdisk boot ... the instant the >>>>>>>> system started, the entire machine rebooted. No bluescreen, just >>>>>>>> black screen then POST. >>>>>>>> >>>>>>>> So no way to capture debug info, either. >>>>>>>> >>>>>>>> So I'm completely stuck ... and this is a huge issue for me ... I do >>>>>>>> major development work under colinux, and they want to retire my XP >>>>>>>> box, since the entire company is migrating to Vista. >>>>>>>> >>>>>>>> Soon I won't be given a choice; I need this working before that >>>>>>>> happens ... >>>>>>>> >>>>>>>> Anyone got any ideas? >>>>>>>> >>>>>>>> Remember ... the image in this case is irrelevant - the problem >>>>>>>> occurs w/the initrd.gz RAM boot. so it's something endemic to within >>>>>>>> colinux and its kernel itself. >>>>>>>> >>>>>>>> - Jonathan >>>>>>>> >>>>>>>> ------------------------------------------------------------------------- > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
|
From: Henry N. <hen...@ar...> - 2008-06-18 08:02:00
|
Hello Steve, thank you for your post. You have self compiled the kernel? Please let us see your used gcc and type inside: "dmesg | head -n1" Please send me your kernel config. Henry Steve Wagner wrote: > I cant help you, but i can say that "Linux colinux 2.6.17-co-0.8.0 #2" > works with Vista SP1 on an Core Duo without any problem for me. > > Steve > > Jonathan Deitch schrieb: >> I saw a definite difference in behavior between the 0.7.3 and the >> "ntflood" 0.8.0 ... >> >> 0.7.3 would cause the system to lockup within a minute ... 0.8.0 ntflood >> would run OK for 4-5 minutes and then lock up (same exact symptoms). >> >> The pictures, unfortunately, do not help. >> >> As I memtioned, this problem occurs with minimal settings (initrd and >> root) booting the initrd ram boot. >> >> No image, no network, no nothing. >> >> If I can't get the RAM boot to work, then there's no point going any >> farther with anything else. >> >> Any ideas? I really need help on this ... if there isn't a solution >> soon, I will probably be forced to abandon using colinux altogether, and >> rethinking my whole way of working. :-( >> >> - Jonathan >> Henry Nestler wrote: >>> I have no Vista running. But from an example of install I have lots of >>> screenshots. Perhaps you will find suggestions from there: >>> http://www.henrynestler.com/colinux/screenshoots/Vista-Album >>> >>> The "ntconsoleflood" is also fixed in coLinux version 0.7.3 final release. >>> >>> Henry >>> >>> Jonathan Deitch wrote: >>> >>>> Whoops ... I spoke too soon. >>>> >>>> The "ntconsoleflood" 0.8.0 version allows the system to boot, and run >>>> for a bit. >>>> >>>> After about 5 minutes, however, the same exact circumstances as before >>>> occur. >>>> >>>> Reproduced with all the same settings (including the barebones /dev/RAM >>>> boot). >>>> >>>> Same symptoms with vista before after colinux shutdown - everything runs >>>> very slow, entire PC is unusable. >>>> >>>> So still no solution. >>>> >>>> - Jonathan >>>> >>>> Jonathan Deitch wrote: >>>> >>>>> OK ... update ... >>>>> >>>>> After diving into the colinux-users archive, I saw a note about the >>>>> 0.8.0 test version for ntconsoleflood ... that actually seems to have >>>>> fixed this issue. >>>>> >>>>> As noted in the email string that led to that test version, the Vista >>>>> Business I'm running it on is a multi-core cpu; this may be another >>>>> example where a SMP setup is breaking the 'older' versions of colinux. >>>>> >>>>> My previous system, is a WinXP P4 2.4 .. which is a single cpu system. >>>>> >>>>> - Jonathan >>>>> >>>>> Jonathan Deitch wrote: >>>>> >>>>>> I've tried every trick I can find on the web, and I can't get /any/ >>>>>> version of colinux running on Vista SP1. >>>>>> >>>>>> Tried 0.7.3 (release version) and the latest 0.8.x development >>>>>> version. Same exact symptom. >>>>>> >>>>>> What happens is the system boots up, and seems to be just fine. >>>>>> >>>>>> After about 60 seconds, /both /the linux /and/ Vista slow to a crawl >>>>>> and neither is usable. >>>>>> >>>>>> Even if you get Colinux shut down, Vista is /still/ slow as molasses >>>>>> and the only recovery is to reboot (and that's if Vista doesn't >>>>>> freeze on shutdown). >>>>>> >>>>>> Tried with multiple system images (various flavors of Linux), same thing. >>>>>> >>>>>> Tried with the bare Ramdisk boot (just initrd.gz) - same thing. >>>>>> >>>>>> Tried to run a debug on the bare ramdisk boot ... the instant the >>>>>> system started, the entire machine rebooted. No bluescreen, just >>>>>> black screen then POST. >>>>>> >>>>>> So no way to capture debug info, either. >>>>>> >>>>>> So I'm completely stuck ... and this is a huge issue for me ... I do >>>>>> major development work under colinux, and they want to retire my XP >>>>>> box, since the entire company is migrating to Vista. >>>>>> >>>>>> Soon I won't be given a choice; I need this working before that >>>>>> happens ... >>>>>> >>>>>> Anyone got any ideas? >>>>>> >>>>>> Remember ... the image in this case is irrelevant - the problem >>>>>> occurs w/the initrd.gz RAM boot. so it's something endemic to within >>>>>> colinux and its kernel itself. >>>>>> >>>>>> - Jonathan >>>>>> >>>>>> ------------------------------------------------------------------------- |
|
From: Jonathan D. <tz...@sp...> - 2008-06-18 17:36:55
|
System is an AMD "turion x 2" cpu, on a laptop, running vista business. As noted, I've been testing directly in ramdisk mode, where the only two options given are initrd.gz and root=dev/ram0 (I think) ... Failure mode is reproduced with that simple setup for all 0.7.3 and newer versions I've tried. Same exact setup is solid as a rock on XP on a P4 2.4. - Jonathan Josep Maria Antolín Segura wrote: > May I ask some more information about the System? > > Here i am running Vista Home Premium SP1 (Spanish) with colinux 0.7.3, on a core > 2 duo laptop (centrino duo) with 2GB of RAM. > The amount of RAM for colinux is 256MB. > > The only problem i had with it was with some random reboots, which in my case, > were due to the problems with ext2 and ext3 fixed recently. > > my config file is as follows: > kernel=vmlinux > > #reenable each time colinux daemon is updated, so that modules can be updated > aswell. > initrd=initrd.gz > > cobd0=D:\Colinux\debian\Debian-etch.ext3.3gb > cobd3=D:\Colinux\debian\swap_128Mb > > cofs0=C:\ > cofs1=D:\ > > > mem=256 > eth0=tuntap > #eth1=pcap-bridge,ethernet > root=/dev/cobd0 > > > Note that I run it as a service, but i've tried running it manually with the > following script with no problems: > c: > cd "c:\Program Files\colinux\" > start colinux-daemon.exe -t nt @D:\Colinux\debian\debian.colinux.conf.txt > start colinux-console-nt.exe > > > > > |
|
From: Josep M. A. S. <ja...@pa...> - 2008-06-18 18:02:06
|
commandline:
colinux-daemon.exe -t nt @D:\Colinux\debian\ramdisk-mode.txt
ramdisk-mode.txt:
kernel=vmlinux
initrd=initrd.gz
root=/dev/ram0
colinux version:
Linux (none) 2.6.22.18-co-0.7.3 #1 PREEMPT Sat May 24 22:27:30 UTC 2008 i686 unk
nown
I don't know if it may be related to being Vista Business, or the AMD chip. I
believe you'll have to work that out with the developers via debug builds.
--
_ _ /~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-\
o o | Josep Ma [JAZ] |
* | ---------------- |
`-´ | Messenger: ja...@ho... |
\-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~/
|
|
From: Jonathan D. <tz...@sp...> - 2008-06-18 19:54:55
|
Tried this in both normal and service mode. In both cases it fails .. runs for a minute or so, then both colinux and vista are very very slow. There are no errors. After that, the machine's screwed. You have to reboot. Debugging is impossible; I tried to set it up, and the second it tries to actually write debugging information, the entire system goes black and reboots; no bluescreen. So still no go. - Jonathan Josep Maria Antolín Segura wrote: > commandline: > colinux-daemon.exe -t nt @D:\Colinux\debian\ramdisk-mode.txt > > ramdisk-mode.txt: > kernel=vmlinux > initrd=initrd.gz > root=/dev/ram0 > > colinux version: > Linux (none) 2.6.22.18-co-0.7.3 #1 PREEMPT Sat May 24 22:27:30 UTC 2008 i686 unk > nown > > > I don't know if it may be related to being Vista Business, or the AMD chip. I > believe you'll have to work that out with the developers via debug builds. > > |
|
From: Paolo M. <pao...@gm...> - 2008-06-20 07:17:50
|
Hi Jonathan,
can you do an other simple test ?
Run colinux on vista.
************************
Then digit :
# n1=$(cat /proc/interrupts | grep "0:" | awk '{ print $2 }')
wait <n> seconds on you hand-clock (Don't use sleep command ! we are
studying the PC timer taht seems broken! ). Then exec a new command
# n2=$(cat /proc/interrupts | grep "0:" | awk '{ print $2 }')
Now digit
# echo $(expr $n2 - $n1)
Get the value and divide it by <n>.
You should have a value very closed to 100. Is it ?
Run an other linux distribution that works
***********************************************
Use the same procedure written above.
You should have 100 or 1000 (or 250) .... Depends on the HZ defined
into kernel ....
What is the value you see ?
Bye,
Paolo
|
|
From: Michelangelo B. <mic...@gm...> - 2008-06-21 16:16:45
|
On 6/20/08, Paolo Minazzi <pao...@gm...> wrote:
>
> Hi Jonathan,
> can you do an other simple test ?
>
> Run colinux on vista.
> ************************
> Then digit :
>
> # n1=$(cat /proc/interrupts | grep "0:" | awk '{ print $2 }')
>
> wait <n> seconds on you hand-clock (Don't use sleep command ! we are
> studying the PC timer taht seems broken! ). Then exec a new command
>
> # n2=$(cat /proc/interrupts | grep "0:" | awk '{ print $2 }')
>
> Now digit
> # echo $(expr $n2 - $n1)
>
> Get the value and divide it by <n>.
>
> You should have a value very closed to 100. Is it ?
>
>
> Run an other linux distribution that works
> ***********************************************
> Use the same procedure written above.
>
> You should have 100 or 1000 (or 250) .... Depends on the HZ defined
> into kernel ....
> What is the value you see ?
>
> Bye,
>
> Paolo
>
>
> -------------------------------------------------------------------------
I've got a Athlon64 x2 with same bios problem (which it had not before last
bios update). I can confirm Ubuntu 7.10 did not pass booting without
acpi=off parameter.
Should this help debugging I can send more data|run some test.
My 2 c
Michelangelo
|
|
From: Henry N. <hen...@ar...> - 2008-06-18 20:46:41
|
Hello, Josep Maria Antolín Segura schrieb: > commandline: > colinux-daemon.exe -t nt @D:\Colinux\debian\ramdisk-mode.txt > > ramdisk-mode.txt: > kernel=vmlinux > initrd=initrd.gz > root=/dev/ram0 > > colinux version: > Linux (none) 2.6.22.18-co-0.7.3 #1 PREEMPT Sat May 24 22:27:30 UTC 2008 i686 unk > nown > > > I don't know if it may be related to being Vista Business, or the AMD chip. I > believe you'll have to work that out with the developers via debug builds. > thanks, Josep. The version 0.8.0 with kernel 2.6.17 is a non official build, please use this not as reference. The version 20080511-ntconsoleflood is a special build with some more add ons, and have more debugging inside. So, this version would run slower. You have seen it as a longer time before problems starts. Jonathan, debugging is available, if you would try some steps. First lets configure the simplest start. Perhaps Josep can check, that the same variant is running without probmlems. 0. All the colinux programs, please run from a CMD.EXE you have opened as Admin. Please don't use "start.exe" and not a tool "runas.exe". Please don't think you are an user with admin rights. That is not the same. Check your admin status with "whoamy /all" or so. 1. You should have installed 0.7.3 final version. We need to verify exactly the same version. Check the installed driver: C:\coLinux> colinux-daemon --status-driver Cooperative Linux Daemon, 0.7.3 Daemon compiled on Sat May 24 22:36:07 2008 checking if the driver is installed current state: 4 (fully initialized) current number of monitors: 0 current linux api version: 10 current periphery api version: 20 Driver compiled on: Sat May 24 22:36:07 2008 The installed path can differ. Any different output would make problems. 2. Open your Windows task manager and watch the performance graph. Splitte the cpu into 2 diagrams to see, if one core is hanging. Some times later as you sayed, the first cpu core (the left diagram) would go into 100% of load after coLinux runs somethere in an endless loop. We need to find the position in Linux kernel boot steps. 3. Read file debugging.txt from your installation, or get it from http://colinux.svn.sourceforge.net/svnroot/colinux/branches/devel/doc/debugging 4. Open a command prompt, change into colinux directory and run: C:\coLinux> mode con lines=600 cols=120 C:\coLinux> colinux-debug-daemon.exe -p -d -s prints=31,misc=31 Adjust the font size from sys-menu of this window to see most lines as you can. Don't worry about XML output needs only to see the text messages. 5. Watch the taskmanager performance graph. This command should not incrace the cpu load. 6. Run the minimal coLinux ramdisk with special parameters: colinux-daemon mem=64 kernel=vmlinux initrd=initrd.gz root=/dev/ram0 rootdelay=10 Any signifikant changes in the memory or performance? 10 to 20% more cpu load is normal after kernel boot, 5-10 MB more memory is normal. 7. Wait for prompt. Do nothing, do not press ENTER before 10 minutes you have seen not your problem. The colinux-debug output should stop on this step. 8. Press ENTER and run "halt" to shutdown coLinux. The debugger should stop with text "string" lines like this: <string>prints "colinux: halted, exiting." <string>shutting down</string> ... <string>Pipe broken, exiting</string> <string>done freeing</string> <string>after free: 0 blocks</string> <string>daemon cleanup</string> <string>rc=00424400 exit=0</string> Please copy and send your last lines, if you have more or others. In every step: Watch also for NT kernel memory usage after every step, and what the physical free memory. Would it incrace permanently after one of the steps? Plese give some coments for the steps. We can rune more debugs later. -- Henry N. |
|
From: Jonathan D. <tz...@sp...> - 2008-06-18 21:08:23
|
I'll run these tests tonight ... However - and this is the puzzling part - when the system goes into the slow-mode, there is no abnormal CPU load. Yep, that's right ... no high CPU in either task manager, or top. Both colinux and Vista are still usable - they're just very very slow with a 4-5 second leg between any action and system response. - Jonathan Henry Nestler wrote: > Hello, > > Josep Maria Antolín Segura schrieb: > >> commandline: >> colinux-daemon.exe -t nt @D:\Colinux\debian\ramdisk-mode.txt >> >> ramdisk-mode.txt: >> kernel=vmlinux >> initrd=initrd.gz >> root=/dev/ram0 >> >> colinux version: >> Linux (none) 2.6.22.18-co-0.7.3 #1 PREEMPT Sat May 24 22:27:30 UTC 2008 i686 unk >> nown >> >> >> I don't know if it may be related to being Vista Business, or the AMD chip. I >> believe you'll have to work that out with the developers via debug builds. >> >> > > thanks, Josep. > > The version 0.8.0 with kernel 2.6.17 is a non official build, please use > this not as reference. > > The version 20080511-ntconsoleflood is a special build with some more > add ons, and have more debugging inside. So, this version would run > slower. You have seen it as a longer time before problems starts. > > Jonathan, debugging is available, if you would try some steps. First > lets configure the simplest start. Perhaps Josep can check, that the > same variant is running without probmlems. > > 0. All the colinux programs, please run from a CMD.EXE you have opened > as Admin. Please don't use "start.exe" and not a tool "runas.exe". > Please don't think you are an user with admin rights. That is not the > same. Check your admin status with "whoamy /all" or so. > > 1. You should have installed 0.7.3 final version. We need to verify > exactly the same version. Check the installed driver: > C:\coLinux> colinux-daemon --status-driver > Cooperative Linux Daemon, 0.7.3 > Daemon compiled on Sat May 24 22:36:07 2008 > > checking if the driver is installed > current state: 4 (fully initialized) > current number of monitors: 0 > current linux api version: 10 > current periphery api version: 20 > Driver compiled on: Sat May 24 22:36:07 2008 > > The installed path can differ. Any different output would make problems. > > 2. Open your Windows task manager and watch the performance graph. > Splitte the cpu into 2 diagrams to see, if one core is hanging. > > Some times later as you sayed, the first cpu core (the left diagram) > would go into 100% of load after coLinux runs somethere in an endless > loop. We need to find the position in Linux kernel boot steps. > > 3. Read file debugging.txt from your installation, or get it from > http://colinux.svn.sourceforge.net/svnroot/colinux/branches/devel/doc/debugging > > 4. Open a command prompt, change into colinux directory and run: > C:\coLinux> mode con lines=600 cols=120 > C:\coLinux> colinux-debug-daemon.exe -p -d -s prints=31,misc=31 > Adjust the font size from sys-menu of this window to see most lines as > you can. Don't worry about XML output needs only to see the text messages. > > 5. Watch the taskmanager performance graph. This command should not > incrace the cpu load. > > 6. Run the minimal coLinux ramdisk with special parameters: > colinux-daemon mem=64 kernel=vmlinux initrd=initrd.gz root=/dev/ram0 > rootdelay=10 > > Any signifikant changes in the memory or performance? 10 to 20% more cpu > load is normal after kernel boot, 5-10 MB more memory is normal. > > 7. Wait for prompt. Do nothing, do not press ENTER before 10 minutes you > have seen not your problem. The colinux-debug output should stop on this > step. > > 8. Press ENTER and run "halt" to shutdown coLinux. The debugger should > stop with text "string" lines like this: > <string>prints "colinux: halted, exiting." > <string>shutting down</string> > ... > <string>Pipe broken, exiting</string> > <string>done freeing</string> > <string>after free: 0 blocks</string> > <string>daemon cleanup</string> > <string>rc=00424400 exit=0</string> > > Please copy and send your last lines, if you have more or others. > > In every step: > Watch also for NT kernel memory usage after every step, and what the > physical free memory. Would it incrace permanently after one of the steps? > > Plese give some coments for the steps. We can rune more debugs later. > > |
|
From: Henry N. <hen...@ar...> - 2008-06-18 23:06:09
|
Jonathan Deitch wrote: > I'll run these tests tonight ... > > However - and this is the puzzling part - when the system goes into the > slow-mode, there is no abnormal CPU load. Yep, that's right ... no high > CPU in either task manager, or top. > > Both colinux and Vista are still usable - they're just very very slow > with a 4-5 second leg between any action and system response. Than I have an idea: The cpu has a buggy or a special timer chip? I have read some about buggy TSC, and Windows has shipped an update for such chips in a service pack. You says, the taskman shows na normal cpu load? Than the sytesm timer was falling down into slow mode? Currently I don't know why coLinux would reprogrammed the timer. Colinux does no change the timer intervall. Not directly, but perhaps the new kernel has some hocks for special cpu's? I will grep for it. The mouse is slow. ok. What is with a keyboard resonse time, for example in a notepad, or in a command prompt? Please boot a knoppix, or from a distribution you have in a rescure mode with text console. Somethere you can cat the native kernel boot messages (dmesg) into a file and send me, please. I will grep for special messages about your cpu. You also can send me the kernel messages from coLinux-daemon.exe, as you can do it via mouse "copy all text" from screen into clipboard and paste it into notepad. Or run "colinux-daemon.exe ... > file.log" -- Henry N. |
|
From: Jonathan D. <tz...@sp...> - 2008-06-18 23:31:20
|
I can get you a knoppix dmesg dump no problem. I can also get you a dump from colinux, more than likely ... while the system does slow down, if you're patient it's still usable ... All functions slow down - mouse, keyboard, heck even the clock on the desktop. Everything starts slowing down, and actions happen only in spurts every 4-5 seconds ... ie: you click something, 4-5 seconds later it happens. You type, 4-5 seconds later it appears. etc. - Jonathan Henry Nestler wrote: > Jonathan Deitch wrote: > >> I'll run these tests tonight ... >> >> However - and this is the puzzling part - when the system goes into the >> slow-mode, there is no abnormal CPU load. Yep, that's right ... no high >> CPU in either task manager, or top. >> >> Both colinux and Vista are still usable - they're just very very slow >> with a 4-5 second leg between any action and system response. >> > > Than I have an idea: The cpu has a buggy or a special timer chip? I have > read some about buggy TSC, and Windows has shipped an update for such > chips in a service pack. > > You says, the taskman shows na normal cpu load? Than the sytesm timer > was falling down into slow mode? Currently I don't know why coLinux > would reprogrammed the timer. Colinux does no change the timer > intervall. Not directly, but perhaps the new kernel has some hocks for > special cpu's? I will grep for it. > > The mouse is slow. ok. What is with a keyboard resonse time, for example > in a notepad, or in a command prompt? > > Please boot a knoppix, or from a distribution you have in a rescure mode > with text console. Somethere you can cat the native kernel boot messages > (dmesg) into a file and send me, please. I will grep for special > messages about your cpu. You also can send me the kernel messages from > coLinux-daemon.exe, as you can do it via mouse "copy all text" from > screen into clipboard and paste it into notepad. Or run > "colinux-daemon.exe ... > file.log" > > |
|
From: Jason A. <ja...@ha...> - 2008-06-18 23:44:37
|
On Wed, Jun 18, 2008 at 7:07 PM, Henry Nestler wrote: > Jonathan Deitch wrote: >> However - and this is the puzzling part - when the system goes into the >> slow-mode, there is no abnormal CPU load. Yep, that's right ... no high >> CPU in either task manager, or top. >> >> Both colinux and Vista are still usable - they're just very very slow >> with a 4-5 second leg between any action and system response. Sounds familiar... > > Than I have an idea: The cpu has a buggy or a special timer chip? I have > read some about buggy TSC, and Windows has shipped an update for such > chips in a service pack. How about an alternative theory? Is your page file usage changing? If so, you can configure your taskman process list to show you memory usage and/or VM size. If something spirals out of control (and it will take a little while to do so), your system will start swapping memory with disk until it's painfully slow. coLinux, however, should not be torturing you with memory leaks. It's not as esoteric a theory as buggy system timer handling, but it's a simple test. Cheers, Jason |
|
From: Jonathan D. <tz...@sp...> - 2008-06-19 15:48:17
|
Ok, Still no go. I cannot get a dump from colinux; when I try and run the debug setup, the system goes blackscreen and reboots. No bluescreen. I tried completely disabling the page file, same behavior. When the problem occurs, I do not see ANY runaway (or abnormal) cpu or memory usage. Anyone got any other ideas? I'm rapidly reaching the point where I'm going to be given no choice by my employer but to abandon colinux as vista incompatible and find another solution. - Jonathan Jason Alonso wrote: > On Wed, Jun 18, 2008 at 7:07 PM, Henry Nestler wrote: > >> Jonathan Deitch wrote: >> >>> However - and this is the puzzling part - when the system goes into the >>> slow-mode, there is no abnormal CPU load. Yep, that's right ... no high >>> CPU in either task manager, or top. >>> >>> Both colinux and Vista are still usable - they're just very very slow >>> with a 4-5 second leg between any action and system response. >>> > > Sounds familiar... > > >> Than I have an idea: The cpu has a buggy or a special timer chip? I have >> read some about buggy TSC, and Windows has shipped an update for such >> chips in a service pack. >> > > How about an alternative theory? Is your page file usage changing? > If so, you can configure your taskman process list to show you memory > usage and/or VM size. If something spirals out of control (and it > will take a little while to do so), your system will start swapping > memory with disk until it's painfully slow. coLinux, however, should > not be torturing you with memory leaks. > > It's not as esoteric a theory as buggy system timer handling, but it's > a simple test. > > Cheers, > Jason > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
|
From: Henry N. <hen...@ar...> - 2008-06-19 20:19:16
|
Can you run "colinux-daemon --status-driver" ? Perhaps we can check it by forcing parameter errors. Please run the follow tests by step and check your mouse after every step. We need to know on what step the problems begins. Abnormal exist of colinux-daemom are ok in that testings. "colinux-daemon mem=32 kernel=missing.file" Lets only driver init, no loading kernel. "colinux-daemon -v 3 mem=32 kernel=missing.file" The same with more debugs. "colinux-daemon -v 3 -d mem=32 kernel=vmlinux root=/dev/dummy" Loads and starts the kernel. Exits before mount filesystem. No console. "colinux-daemon -v 3 -t nt mem=32 kernel=vmlinux root=/dev/dummy" The same with NT console. "colinux-daemon -v 3 mem=32 kernel=vmlinux root=/dev/dummy" The same with FLTK console. "colinux-daemon -v 3 -d mem=32 kernel=vmlinux initrd=initrd.gz root=/dev/ram0 init=/sbin/halt" Starts RAMdisk and shuting down Linux automaticly, without console. "colinux-daemon -v 3 mem=32 kernel=vmlinux initrd=initrd.gz root=/dev/ram0 init=/sbin/halt" The same with FLTK console. "colinux-daemon mem=32 kernel=vmlinux initrd=initrd.gz root=/dev/ram0 init=/sbin/halt" The same with less error checks. -- Henry Jonathan Deitch wrote: > Ok, > > Still no go. I cannot get a dump from colinux; when I try and run the > debug setup, the system goes blackscreen and reboots. No bluescreen. > > I tried completely disabling the page file, same behavior. > > When the problem occurs, I do not see ANY runaway (or abnormal) cpu or > memory usage. > > Anyone got any other ideas? I'm rapidly reaching the point where I'm > going to be given no choice by my employer but to abandon colinux as > vista incompatible and find another solution. > > - Jonathan > > Jason Alonso wrote: >> On Wed, Jun 18, 2008 at 7:07 PM, Henry Nestler wrote: >> >>> Jonathan Deitch wrote: >>> >>>> However - and this is the puzzling part - when the system goes into the >>>> slow-mode, there is no abnormal CPU load. Yep, that's right ... no high >>>> CPU in either task manager, or top. >>>> >>>> Both colinux and Vista are still usable - they're just very very slow >>>> with a 4-5 second leg between any action and system response. >>>> >> Sounds familiar... >> >> >>> Than I have an idea: The cpu has a buggy or a special timer chip? I have >>> read some about buggy TSC, and Windows has shipped an update for such >>> chips in a service pack. >>> >> How about an alternative theory? Is your page file usage changing? >> If so, you can configure your taskman process list to show you memory >> usage and/or VM size. If something spirals out of control (and it >> will take a little while to do so), your system will start swapping >> memory with disk until it's painfully slow. coLinux, however, should >> not be torturing you with memory leaks. >> >> It's not as esoteric a theory as buggy system timer handling, but it's >> a simple test. >> >> Cheers, >> Jason >> |
|
From: Jonathan D. <tz...@sp...> - 2008-06-19 16:29:37
|
Henry - capturing dmesg from knoppix will have to wait a bit ... I didn't realize the distro had moved from CD to DVD, hence the download is taking a bit longer. - Jonathan Henry Nestler wrote: > Jonathan Deitch wrote: > >> I'll run these tests tonight ... >> >> However - and this is the puzzling part - when the system goes into the >> slow-mode, there is no abnormal CPU load. Yep, that's right ... no high >> CPU in either task manager, or top. >> >> Both colinux and Vista are still usable - they're just very very slow >> with a 4-5 second leg between any action and system response. >> > > Than I have an idea: The cpu has a buggy or a special timer chip? I have > read some about buggy TSC, and Windows has shipped an update for such > chips in a service pack. > > You says, the taskman shows na normal cpu load? Than the sytesm timer > was falling down into slow mode? Currently I don't know why coLinux > would reprogrammed the timer. Colinux does no change the timer > intervall. Not directly, but perhaps the new kernel has some hocks for > special cpu's? I will grep for it. > > The mouse is slow. ok. What is with a keyboard resonse time, for example > in a notepad, or in a command prompt? > > Please boot a knoppix, or from a distribution you have in a rescure mode > with text console. Somethere you can cat the native kernel boot messages > (dmesg) into a file and send me, please. I will grep for special > messages about your cpu. You also can send me the kernel messages from > coLinux-daemon.exe, as you can do it via mouse "copy all text" from > screen into clipboard and paste it into notepad. Or run > "colinux-daemon.exe ... > file.log" > > |
×
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