On 25 January 2011 23:21, Russell Dickenson <russelldicken...@gmail.com>wrote:
> On 25 January 2011 21:48, Miklos Vajna <vmik...@frugalware.org> wrote: > > On Tue, Jan 25, 2011 at 09:46:19AM +1000, Russell Dickenson < > russelldicken...@gmail.com> wrote: > >> I recently reported and discussed in the dev IRC channel a problem > >> where my MSI Wind U200 won't boot with the 2.6.36 series kernel. Last > >> night I did a complete "pacman-g2 -Syu", including kernel, to see if > >> the 2.6.37 kernel would boot and it did! Yay! However it now won't > >> boot properly, possibly because of my early experimentation with the > >> systemd repository. I am going to completely reinstall Frugalware and > >> try again with a later kernel but sysvinit init scripts. I have to > >> reinstall from 1.3 first because I could not boot to the USB image of > >> the FW 1.4 RC1 because it contains kernel 2.6.36. > > > > I just uploaded frugalware-1.4rc1.708.g9984339-i686-usb.img to the > > -current-iso directory, containing 2.6.37. > > Thanks. When I get a chance I'll test it. > > > And recently you can experiment with systemd easily: > > > > http://wiki.frugalware.org/index.php/Systemd#Installation > > I think that in testing the system WIP repo too early I broke > something serious. Every time I install sysvinit I find that the run > level scripts don't run. Anyway I have successfully reinstalled 1.3 > from the USB image and will bring this up to 1.4rc1+, then test newest > kernel and systemd. > > > Whenever something gets broken, you can just remove that extra kernel > > parameter and you have sysvinit back. > OK, I just changed pacman's configuration so that it was sync-ed against current and did a "pacman-g2 -Syu". I then installed systemd but it complained that there were many existing files already in the filesystem. I double checked the wiki and decided to force the installation of systemd. The laptop successfully boots with kernel-2.6.37-fw1 but something in the boot sequence gets a fatal error, although the boot sequence continues regardless. I'll check what's getting the fatal error and confirm what I need to do to fix it. I'm very happy that the laptop is booting to 2.6.37 kernel, though, so I can continue using Frugalware. :) -- May you always be Frugal, Russell Dickenson (AKA phayz)
_______________________________________________ Frugalware-devel mailing list Frugalware-devel@frugalware.org http://frugalware.org/mailman/listinfo/frugalware-devel
