Christian Weisgerber <na...@mips.inka.de> wrote: > Paul de Weerd: > > > http://www.weirdnet.nl/openbsd/serial_script/v215.txt > > Puzzling. Seeing stuff like this... > > ----------------------------> > Automatic boot in progress: starting file system checks. > /dev/sd0a (e580d48835930ea5.a): file system is clean; not checking > /dev/sd0k (e580d48835930ea5.k): file system is clean; not checking > /dev/sd1a (b4b681cb78013c36.a): file system is clean; not checking > /dev/sd0d (e580d48835930ea5.d): file system is clean; not checking > /dev/sd1d (b4b681cb78013c36.d): file system is clean; not checking > /dev/sd0f (e580d48835930ea5.f): file system is clean; not checking > /dev/sd0g (e580d48835930ea5.g): file system is clean; not checking > /dev/sd0h (e580d48835930ea5.h): file system is clean; not checking > /dev/sd0j (e580d48835930ea5.j): file system is clean; not checking > Automa/dev/sd0i (e580d48835930ea5.i): file system is clean; not checking > tic boot in progress: st/dev/sd0e (e580d48835930ea5.e): file system is > clean; not checking > arting file system checks. > <---------------------------- > > ... I wonder: Did you reboot inbetween and there was a huge loss > of output, or does it actually repeat output? The latter would be > particularly inexplicable. > > > Will this work at all with the uplcom(4) device, > > It certainly should. > > > or do I need a true serial port on a machine somewhere? > > No. I have used uplcom(4) and uftdi(4) serial adapters to access > serial consoles since... since well before I got rid of my alpha > and sparc64 gear.
I have recently gotten my hand on a batch of uftdi(4) that were so defective that I threw them in the garbage. I believe they were clones, and operationally just a wee bit off. Two behaviours were very bad: they would misbehave on the usb bus at times, and they would suddenly repeat a chunk of characters. It is odd that is not a power of two, looks like 67 or maybe 68...
