Hi all,
I run across a similar issue after upgrading from astlinux 1.2.6.1_1.8.37 to 1.2.7_1.8.37 on a x86_64 board. After lots of debugging the issue was that the "rootdelay=10" kernel option on the .run.conf file needed for my external USB flash to boot was lost in the upgrading process. I'm not sure if that was caused by the upgrading script or it was my fault for not rebooting after running the "upgrade with new firmware" and before running the "upgrade with new runnix" scripts (instead I run both update scripts in a row and rebooted later). After making a fresh 1.2.7 install and restoring my old ASTURW partition on it everything worked again. I hope this helps somebody. Regards. Gonzalo Ibáñez ---------------------------------------------------------------------- Message: 1 Date: Thu, 4 Aug 2016 05:16:10 +0000 From: Michael Knill <michael.kn...@ipcsolutions.com.au> Subject: Re: [Astlinux-users] Still problems with 1.2.7 To: AstLinux Users Mailing List <astlinux-users@lists.sourceforge.net> Message-ID: <799ce109-17d8-4d26-99ca-c1001bd58...@ipcsolutions.com.au> Content-Type: text/plain; charset="utf-8" Thanks Lonnie for your testing. Really appreciate it. It must be something funny with my setup. I wonder if the problem is with my 1.2.6.1 installer? Unfortunately I decided to take the opportunity to build new on x86_64 so I cant really do any more testing for this but I will need to watch out for this issue. 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 2:53 PM To: AstLinux List <astlinux-users@lists.sourceforge.net> Subject: Re: [Astlinux-users] Still problems with 1.2.7 Hi Michael, I spent a couple hours extensively testing, bottom line, it worked perfectly for me, I could not reproduce your "too big device loop0" etc. error after reverting back to 1.2.6.1 . The details ... I dusted off an old Jetway NF96FL-525-LF with a 1 GB Emphase IDE DOM, a geni586-serial image with Asterisk 11. Since the box had an old version, I first upgraded to 1.2.6.1 extracted from the mirror.astlinux-project.org repository (I had to use an intermediate private repo to set the 'ver' file) All went well. I then upgraded using the Repository URL: http://mirror.astlinux-project.org/ast11-firmware-1.x to upgrade to 1.2.7 . All went well. I then reverted to the previous image (1.2.6.1), worked fine. I went back and forth several times, using both reboot and kernel-reboot. All worked. So then I started of scratch, I dd'ed the 1.2.6.1 Installer ISO to a USB drive, persuaded the Jetway BIOS to boot from USB and installed a fresh 1.2.6.1 via the AstLinux Installer (wow, that IDE DOM is very slow). I did a Initial configuration as normal, and 1.2.6.1 was running. I then upgraded to 1.2.7, reverted back to 1.2.6.1, back and forth several times, using both reboot and kernel-reboot. All worked. So, I don't know what to tell you Michael. Possibly you might want to try "dosfsck" to try to find any errors on your /dev/sda1 FAT16 partition. You may also try while in 1.2.7 "upgrade-RUNNIX-image upgrade" to install the latest RUNNIX bootloader, but I don't think that is the issue, but no harm to try. Hopefully these details may help you. Lonnie On Aug 3, 2016, at 5:58 PM, Lonnie Abelbeck <li...@lonnie.abelbeck.com> wrote: > 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.
