Lots of good information here. I wish all users were as diligent. The results of stty show some small differences from mine. For example, you have -iexten (the dash means negation), while I have iexten, which means mine enables non-POSIX special characters and yours doesn't. That could matter. Most of the others have to do with echoing characters and translating CR/LF, etc. Some of them could also matter.
Try setting it to "sane" values. This will basically force your values to mine. *stty sane -F /dev/ttyS0* Then try again. That's all I can think of. -tk On Thu, Nov 26, 2020 at 5:10 PM kiwigander <[email protected]> wrote: > The new machine is an XCY (that's the brand; bought on AliExpress) fanless > mini-PC, Celeron N4100 CPU, 8 GB RAM, 128 GB SSD, 2x gigabit Ethernet, 2x > RS232, 4x USB (looks like USB 2.0). Video is temporarily via HDMI (once > the server is set up, that will be disconnected); internet is via Ethernet > (unit has Wi-Fi built in but I have switched it off in Network Manager); > Apple keyboard is plugged into a USB port and Logitech M570 trackball > communicates through Logi Unifying Receiver plugged into Apple keyboard > (again, once the server is set up, the keyboard will be disconnected). > > New OS is Linux Mint 20. Output of uname -a is as follows: > > Linux XCY 5.4.0-54-generic #60-Ubuntu SMP Fri Nov 6 10:37:59 UTC 2020 > x86_64 x86_64 x86_64 GNU/Linux > > Output of lsusb is as follows: > > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver > Bus 001 Device 003: ID 05ac:024f Apple, Inc. Keyboard Hub > Bus 001 Device 002: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > Output of stty -a -F /dev/ttyS0 is as follows: > > speed 19200 baud; rows 0; columns 0; line = 0; > intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>; > eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = > ^R; > werase = ^W; lnext = ^V; discard = ^O; min = 0; time = 0; > -parenb -parodd -cmspar cs8 hupcl -cstopb cread clocal -crtscts > -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon > -ixoff > -iuclc -ixany -imaxbel -iutf8 > -opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 > vt0 ff0 > -isig -icanon -iexten -echo -echoe -echok -echonl -noflsh -xcase -tostop > -echoprt > -echoctl -echoke -flusho -extproc > > Output of sudo cat /proc/tty/driver/serial (truncated after line 4 as > lines 4 through 31 are identical) is as follows: > > serinfo:1.0 driver revision: > 0: uart:16550A port:000003F8 irq:4 tx:610 rx:1151 fe:45 brk:33 DSR|CD|RI > 1: uart:16550A port:000002F8 irq:3 tx:0 rx:0 DSR|CD|RI > 2: uart:unknown port:000003E8 irq:4 > 3: uart:unknown port:000002E8 irq:3 > 4: uart:unknown port:00000000 irq:0 > > The output of that command is just a snapshot. The first time I repeated > it, the tx:, rx: and fe: values did increment (635, 1166, 46, 45) so > something was trying to communicate through ttyS0. Now they seem to be > static. > > If human memory is correct, COM1=ttyS0=irq4 and COM2=ttyS1=irq3 since > forever, so the serial ports don't seem to be non-standard. > > I've looped the serial cable through a ferrite sleeve; no difference. > > Output of sudo tail -f /var/log/syslog on a fresh cold boot is as follows: > > Nov 27 11:40:52 XCY weewx[759] CRITICAL weewx.engine: **** > Vantage.__init__(self, **config_dict[DRIVER_NAME]) > Nov 27 11:40:52 XCY weewx[759] CRITICAL weewx.engine: **** File > "/home/weewx/bin/weewx/drivers/vantage.py", line 515, in __init__ > Nov 27 11:40:52 XCY weewx[759] CRITICAL weewx.engine: **** > self._setup() > Nov 27 11:40:52 XCY weewx[759] CRITICAL weewx.engine: **** File > "/home/weewx/bin/weewx/drivers/vantage.py", line 1330, in _setup > Nov 27 11:40:52 XCY weewx[759] CRITICAL weewx.engine: **** > self.altitude = self._getEEPROM_value(0x0F, "<h")[0] > Nov 27 11:40:52 XCY weewx[759] CRITICAL weewx.engine: **** File > "/home/weewx/bin/weewx/drivers/vantage.py", line 1398, in _getEEPROM_value > Nov 27 11:40:52 XCY weewx[759] CRITICAL weewx.engine: **** raise > weewx.RetriesExceeded("While getting EEPROM data value at address 0x%X" % > offset) > Nov 27 11:40:52 XCY weewx[759] CRITICAL weewx.engine: **** > weewx.RetriesExceeded: While getting EEPROM data value at address 0xF > Nov 27 11:40:52 XCY weewx[759] CRITICAL __main__: Unable to load driver: > While getting EEPROM data value at address 0xF > Nov 27 11:40:52 XCY weewx[759] CRITICAL __main__: **** Exiting... > > (everything after that seems to involve the NTP daemon) > > Now (after a lunch break) I've run sudo service weewx status and got the > following: > > Nov 27 12:31:30 XCY weewxd[4546]: weewx[4546] CRITICAL weewx.engine: > **** Vantage.__init__(self, **config_dict[DRIVER_NAME]) > Nov 27 12:31:30 XCY weewxd[4546]: weewx[4546] CRITICAL weewx.engine: > **** File "/home/weewx/bin/weewx/drivers/vantage.py", line 515, in > __init__ > Nov 27 12:31:30 XCY weewxd[4546]: weewx[4546] CRITICAL weewx.engine: > **** self._setup() > Nov 27 12:31:30 XCY weewxd[4546]: weewx[4546] CRITICAL weewx.engine: > **** File "/home/weewx/bin/weewx/drivers/vantage.py", line 1321, in > _setup > Nov 27 12:31:30 XCY weewxd[4546]: weewx[4546] CRITICAL weewx.engine: > **** self.hardware_type = self._determine_hardware() > Nov 27 12:31:30 XCY weewxd[4546]: weewx[4546] CRITICAL weewx.engine: > **** File "/home/weewx/bin/weewx/drivers/vantage.py", line 1312, in > _deter> > Nov 27 12:31:30 XCY weewxd[4546]: weewx[4546] CRITICAL weewx.engine: > **** raise weewx.WeeWxIOError("Unable to read hardware type") > Nov 27 12:31:30 XCY weewxd[4546]: weewx[4546] CRITICAL weewx.engine: > **** weewx.WeeWxIOError: Unable to read hardware type > Nov 27 12:31:30 XCY weewxd[4546]: weewx[4546] CRITICAL __main__: Unable to > load driver: Unable to read hardware type > Nov 27 12:31:30 XCY weewxd[4546]: weewx[4546] CRITICAL __main__: **** > Exiting... > > I'll try the other RS232 port. > > > > On Friday, November 27, 2020 at 10:33:36 AM UTC+13 vince wrote: > >> Serial ports will make you pull your hair out for sure... >> >> Lets start with figuring out what your box thinks it sees... >> Please post the output of: >> >> - lsusb >> - dmesg >> - syslog for the period after a clean powerdown/powerup until you see >> a login >> >> Also give us some details about: >> >> - your precise hardware config - what computer make+model etc. >> - which os+version you're running >> >> Also check out >> https://www.cyberciti.biz/faq/find-out-linux-serial-ports-with-setserial/ >> for some other stuff to perhaps try. >> >> Does the new box have serial ports ? It might be worth thinking about a >> serial2usb adaptor as an alternate mechanism for hooking things up. >> Sometimes the few bucks for one is less than the value of your time and >> stress battling things.... >> >> But if you have time, give us the details above so we can get more eyes >> on the problem... >> >> -- > You received this message because you are subscribed to the Google Groups > "weewx-user" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/2604bd6d-fd1e-46c4-9eb9-4dc0d7cc91b6n%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/2604bd6d-fd1e-46c4-9eb9-4dc0d7cc91b6n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAPq0zEDvWS9fmNEA7dUadvTAdfDyr5ersRsVV0ssA9FuuqAumg%40mail.gmail.com.
