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 > |