[ARMedslack] Updating to 14.0 with kernel 2.6.38
I'm thinking of updating to 14.0 on my AC100 (that unfortunately still runs on ubuntu based kernel ... that I learn is actually a fork of chromeos kernel) ... Will things like udev break un kernel 2.6.28 ? Anyone think of anything else I should watcout for ? Regards David ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Initrd fails to mount rootfs
The fact that it worked with 13.37 doesn't really mean a lot, to be honest. 13.37 had a different version of busybox, a different version of udev, a different kernel; most likely containted a different set of modules. Yes, of course. Just wanted to make sure that everything else is ok and I already had it running with 13.37 some time ago. So I gave it a test run. When I had a similar problem myself, I unpacked the kirkwood's initrd and put in the classic print statements into the init script to find out where it was broken. I've built my own kernel now (same version like 14.0 and based on your config). I've just added the needed drivers to the kernel (USB, SCSI disk, some filesystems) so I can boot without initrd and everything is ok now. -- Thorsten Mühlfelder Salix OS: www.salixos.org ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Updating to 14.0 with kernel 2.6.38
Ok it appears that a new package is mandatory for udev to do it's work. Actually I think it's mandatory for modprobe which in turn is mandatory for udev. Manually installing kmod package put things right. If I'd listened to slackpkg man page better by doing first slackpkg install-new probably things would have worked better. Sorry for making a racket ... and hope this can save trouble to other people updating. David Da: Davide louigi...@yahoo.it A: Slackware ARM port armedslack@lists.armedslack.org Inviato: Venerdì 7 Dicembre 2012 15:09 Oggetto: Re: [ARMedslack] Updating to 14.0 with kernel 2.6.38 The odd thing is that I actually was already 14.0 but from a previous current. Indeed I had a few problems with udev and gnutls. It also took forever to get a login prompt (and not sure if CTRL^D/C helped killing something that was not working). Udev stopped working properly and I hadto load manually usb networking interface. I'm sure I;ll have more trouble ahead for this. While doing slackpkg upgrade n gnutl came before wget and then wget stopped working ... this stopped slackpkg from downloading anything Thankgod scp still worked and I was able to get the new whet installed to go on with the upgrade process. As soon as I'm done with the upgrading I'll try posting the udev error messages and see if anyone can help me put it right. Regards David Da: Davide louigi...@yahoo.it A: Slackware ARM port armedslack@lists.armedslack.org Inviato: Venerdì 7 Dicembre 2012 12:36 Oggetto: [ARMedslack] Updating to 14.0 with kernel 2.6.38 I'm thinking of updating to 14.0 on my AC100 (that unfortunately still runs on ubuntu based kernel ... that I learn is actually a fork of chromeos kernel) ... Will things like udev break un kernel 2.6.28 ? Anyone think of anything else I should watcout for ? Regards David ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
