In a strange turn of events o ended up checking the com port bios settings and switching from "enabled" to "automatic" made everything work. At that point I had purged all of nut and installed apcupsd which is also where the 'dumb' type came from. Since it's working I didn't bother going back to nut.
On Fri, Apr 22, 2022, 06:00 Jim Klimov <[email protected]> wrote: > I don't see any mention of a "dumb" driver in sources, so first please > check you've got a useful driver name there. > > Also you may have to chown/chmod the devfs sockets to let your packaged > run-time user/group accounts for NUT daemons access them. > > On Thu, Apr 21, 2022, 18:47 Philippe LeCavalier via Nut-upsuser < > [email protected]> wrote: > >> I'm trying to connect my debian box to an apc smart-ups SC 450 with >> serial port only. The debian box has a serial male port. I' got nut-server >> and client installed put dumb as the driver. >> >> Debian 10.7 >> nut-server 2.7.4-8 >> >> driver = dumb >> port = /dev/ttyS0 >> cable = 940-0024E >> 00:02: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A >> >> I also bought a cable with a FTDI chip which Debian sees as ttyUSB0 but >> that isn't working either. >> >> All I ever get is Driver not connected. >> >> Thanks, Phil >> _______________________________________________ >> Nut-upsuser mailing list >> [email protected] >> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser >> >
_______________________________________________ Nut-upsuser mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
