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 |