To reduce possible faliures to a minimum I did the same with clashNG. Maybe I did not look well enough the first time but this time I got for sure another intresting message before init killing itself: Kernel too old
Don't think a picture is necessary for that. Now I'm not 100% sure that I also had this on slackware 13.1 miniroot but since I use slackware 13.1 to build clashNG I'm strongly suspecting that I had the same message but did not notice it since it wan not on the last line. Damn .... Anyone know what boot loader is on the AC100 ... maybe it's possible to have more then one kernel lingering around ? Anyone know how to build kernel for the ac100 that will run armedslack ? Regards David --- Ven 15/7/11, Thorsten Mühlfelder <thenk...@gmx.de> ha scritto: > Da: Thorsten Mühlfelder <thenk...@gmx.de> > Oggetto: Re: [ARMedslack] Got a toshiba AC100 > A: "Slackware ARM port" <armedslack@lists.armedslack.org> > Data: Venerdì 15 luglio 2011, 10:14 > Am Friday 15 July 2011 09:21:53 > schrieb Davide: > > Ok I followed instructions from http://ac100.gudinna.com/README/ to get > > ubuntoo 10.10 working off the SD. > > > > I then mixed up an armedslack miniroot 13.1 (any > higher would hit the udev > > kernel version requirement issue) with the kernel > modules from ubuntu 10.10 > > for ac100 in an attempt to get a base system booting > off the SD. > > > > All looked right while starting to boot until I hit a > kernel panic: > > attempting to kill init > > Could you make some photos of the interesting error > messages? If you do, don't > attach them to the mail. Instead upload them to an image > hoster. > > > -- > Thorsten Mühlfelder > Salix OS: www.salixos.org > _______________________________________________ > 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
