Yes my office system appears to be working fine after rebuild. It's a Jetway NF96 I think using a SATA Transcend 2G flash.
My build system is an APU with 32G Kingston mSATA. It also seemed to be working fine until I reverted the upgrade. PS I didn't revert because of a problem if that's what you are concerned about. So Im pretty sure that 1.2.7 is working fine but Im a little concerned about an upgrade considering there is currently no return. Is there any way I can boot 1.2.7 again on my build APU as I am concerned I have not backed up everything. Regards Michael Knill -----Original Message----- From: Lonnie Abelbeck <li...@lonnie.abelbeck.com> Reply-To: AstLinux List <astlinux-users@lists.sourceforge.net> Date: Thursday, 4 August 2016 at 8:58 AM To: AstLinux List <astlinux-users@lists.sourceforge.net> Subject: Re: [Astlinux-users] Still problems with 1.2.7 Michael, I will look into that, but more importantly is AstLinux 1.2.7 working as expected ? (given you solved your adaptive ban issue) What hardware are you using ? What flash meda to you have, size, type, and manufacturer ? Lonnie On Aug 3, 2016, at 5:47 PM, Michael Knill <michael.kn...@ipcsolutions.com.au> wrote: > Ok my problem with my office system was not corrupt storage as I performed > the same thing on my build system and it has done EXACTLY the same thing. > I’m not going stupid (stupider) after all. > > I upgraded to 1.2.7 i686 and then reverted to 1.2.6.1 i686 and this is what I > receive when booting: > > ----- > Runnix version 'runnix-0.4-7583' starting... > Skip Verifying astlinux-1.2.6.1.run > losetup: /mnt/base/os/astbio too big device loop0 (2 > 0) > linux-1.2.6.1.ruEXT2-fs (loop0): error: unable to read superblock > n: failed to setup loop device: No such file or directory > mount: mounting /dev/loop0 on /mnt/root failed: Invalid argument > Error mounting astlinux-1.2.6.1.run root fs > Configuring eth0 with DHCP... > udhcpc (v1.19.4) started > r8169 0000:01:00.0: eth0: unable to load firmware patch rtl_nic/rtl8168e-2.fw > (-2) > r8169 0000:01:00.0: eth0: link down > r8169 0000:01:00.0: eth0: link down > Sending discover... > r8169 0000:01:00.0: eth0: link up > Sending discover... > Sending discover... > No lease, failing > Dropping to shell, type 'exit' to reboot > /bin/sh: can't access tty; job control turned off > runnix# > ----- > > Certainly a significant problem. Any ideas? > > Regards > Michael Knill > > ------------------------------------------------------------------------------ > _______________________________________________ > Astlinux-users mailing list > Astlinux-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pay...@krisk.org. ------------------------------------------------------------------------------ _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org. ------------------------------------------------------------------------------ _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
