Hi all, In an attempt to resurrect some old machines (and test some 6.5 snaps), I pulled out a bunch of old sparc64 machines from storage yesterday. These have been shelved for a very long time (and i've tossed two out because they have definitely failed).
Unfortunately, I've not been able to type anything useful on the serial console. So my current thought is that this simply doesn't work with the USB to serial adapter I'm trying: uplcom0 at uhub3 port 1 configuration 1 interface 0 "Prolific Technology Inc. USB-Serial Controller" rev 1.10/3.00 addr 9 Could there be pin-out or flow control issues that allow incoming data (from serial console on the sparc64 box to the cu(1) running on my laptop with this uplcom(4)), but that give erratic behavior when trying to type? Pressing enter once at a login prompt gives me: Please login: Please login: Please login: Please login: Please login: Sun(tm) Advanced Lights Out Man Please Enter password: I've uploaded a couple of script(1) typescripts for the four machines I tried that have the cu session output captured: http://www.weirdnet.nl/openbsd/serial_script/v210_1.txt http://www.weirdnet.nl/openbsd/serial_script/v210_2.txt http://www.weirdnet.nl/openbsd/serial_script/v215.txt http://www.weirdnet.nl/openbsd/serial_script/solair_workstation.txt In all cases I just did `script -c "cu -l cuaU0"`, none of them properly responds to any input on the console. The solair machine doesn't respond at all, it just sits there, the v210 machines don't boot (admittedly, I forgot the ALOM password, but I can't type it in either). The v215 actually boots into an old OpenBSD 5.3 install but has completely garbled up output after it boots. Any advice on how to get any of these going again? Will this work at all with the uplcom(4) device, or do I need a true serial port on a machine somewhere? Thanks, Paul 'WEiRD' de Weerd -- >++++++++[<++++++++++>-]<+++++++.>+++[<------>-]<.>+++[<+ +++++++++++>-]<.>++[<------------>-]<+.--------------.[-] http://www.weirdnet.nl/
