On Aug 2, 2016, at 9:18 AM, David Kerr <da...@kerr.net> wrote:

> Lonnie. It could be the terminal emulator.  I have the same problem using 
> "screen" on Apple Mac.  But if I run screen from Ubuntu Linux it works fine. 

Agree, there is something really messed-up with OS-X's "screen" command.  I 
just wasted a couple hours playing with it, for me OS-X's screen was sending 
extraneous <RETURN>'s.

Additionally AstLinux works fine :-) using screen on AstLinux with a supported 
USB to serial dongle "screen /dev/ttyUSB0 19200" from a terminal session 
worked, kind of crazy but good to know.

I also tried minicom (v2.7) on my Chromebook (in developer mode) "minicom -D 
/dev/ttyUSB0 -v 19200" worked fine.

Lonnie


On Aug 2, 2016, at 9:58 AM, Lonnie Abelbeck <li...@lonnie.abelbeck.com> wrote:

> Hi David,
> 
> Good info, I use "minicom 2.2" (free) on my OS X 10.6.8 Macbook for many 
> years and it has always worked.
> 
> The old minicom URL is not reachable, but the wayback machine finds it, For 
> the trusting, scroll to the bottom of:
> https://web.archive.org/web/20150405144440/http://turin.nss.udel.edu/programming/
> 
> I'm sure there are better ways of getting minicom for OS X today.
> 
> Regardless, you *should* be able to navigate the AstLinux ISO Installer 
> without using arrow keys.
> 
> For all you VT100 aficionados out there, the VT100 keypad has two modes 
> "Standard" and "Applications". For example, Arrow UP in standard mode is "ESC 
> [ A", applications mode is "ESC O A" .  I'm sure standard-mode is what 
> dialog/ncurses is expecting.
> 
> Lonnie
> 
> 
> On Aug 2, 2016, at 9:18 AM, David Kerr <da...@kerr.net> wrote:
> 
>> Lonnie. It could be the terminal emulator.  I have the same problem using 
>> "screen" on Apple Mac.  But if I run screen from Ubuntu Linux it works fine. 
>>  I have not found a free terminal emulator for Mac that I can use Astlinux 
>> boot console with. 
>> 
>> David. 
>> 
>> On Tuesday, August 2, 2016, Lonnie Abelbeck <li...@lonnie.abelbeck.com> 
>> wrote:
>> Hi Michael,
>> 
>> First, I tried the "astlinux-1.2.7-genx86_64-serial.iso" dd'ed to USB drive, 
>> booted on an APU2 with attached serial terminal (minicom) at 19200 baud.  
>> Worked perfectly, arrow keys navigated the menus, installed, removed USB 
>> drive and it booted as expected.  Possibly your terminal program was not 
>> sending the arrow keys properly ?  Each menu item also has a single key 
>> associated with it, the install image selection has '1', '2', or '3' .
>> 
>> I also tried the official production astlinux-1.2.7 upgrade for 
>> genx86_64-serial (APU2) and it worked as expected.
>> 
>>> From your log info below, this seems like you typed "ssh" at the RUNNIX 
>>> boot prompt ...
>> 
>> The "error: unable to read superblock" and "failed to setup loop device"" 
>> does look bad, could well be a failing (failed) SSD.
>> 
>> Lonnie
>> 
>> 
>> 
>> On Aug 2, 2016, at 7:41 AM, Michael Knill 
>> <michael.kn...@ipcsolutions.com.au> wrote:
>> 
>>> Hi guys
>>> 
>>> Well tonight has not been a good night. I upgraded my system to 1.2.7 which 
>>> seemed to go ok but when I noticed a routing problem, I reverted to see if 
>>> it was a release issue.
>>> Well that was the end of that with the following on the console:
>>> 
>>> ----
>>> Runnix version 'runnix-0.4-7583' starting...
>>> Skip Verifying abio too big device loop0 (2 > 0)
>>> stlinux-1.2.6.1.EXT2-fs (loop0): error: unable to read superblock
>>> run
>>> losetup: /mnt/base/os/astlinux-1.2.6.1.run: failed to setup loop device: No 
>>> such file or directory
>>> mount: mounting /dev/loop0 on /mnt/root failed: Invalid argument
>>> Error8021q: adding VLAN 0 to HW filter on device eth0
>>> mounting astlinux-1.2.6.1.run root fs
>>> Configuring eth0 with DHCP...
>>> udhcpc (v1.19.4) started
>>> Sending discover...
>>> e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
>>> e1000e 0000:02:00.0: eth0: 10/100 speed: disabling TSO
>>> 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#
>>> ---
>>> 
>>> Is this a corrupt Flash Drive? I assumed so and I began a rebuild. After my 
>>> serial to USB adaptor crashed my Mac a couple of times and I finally pulled 
>>> the server out of the rack to set the boot order, I am booting a USB with 
>>> astlinux-1.2.7-genx86_64-serial.iso and set my serial port to 19200. 
>>> However I see everything but I cant seem to move the cursor in the menu 
>>> when it comes up.
>>> Any ideas?
>>> 
>>> I am going to bed in disgust ☹
>>> 
>>> 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.
>> 
>> 
>> -- 
>> David Kerr
>> Sent from Gmail Mobile
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> 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.

Reply via email to