search for: ttyu0

Hi. I have some problems with USB->Serial FTDI FT232BM chip drivers on FreeBSD 7.0... FreeBSD recognize the USB device, but when I making connection to /dev/cuaU0 or /dev/ttyU0 I cant send & receive any data from device. cu -l/dev/cuaU0 -s9600 - No response at all, can't even quit the program cu -l/dev/ttyU0 -s9600 - Sometimes working, but few bites/chars after - no response... Sometimes I have error message like: ucom0: open bluk out error (addr 2): IN_USE Tha...

...bps) pwr=SAVE (0mA) ugen2.1: <EHCI root HUB Intel>at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen1.2:<APC USB SERIAL CONVERTER. APC BY SCHNEIDER ELECTRIC> at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) And here are the devices I get after pluging it in: ttyU0 ttyU0.init ttyU0.lock cuaU0 cuaU0.init cuaU0.lock ugen1.2 (ugen1.2 -> usb/1.2.0) (no umodem0 device shows) ** ups.conf [lobos] driver = solis port = /dev/ttyU0 (or cuaU0, or ugen1.2) *** RESULTS ** ugen1.2 [>]/usr/local/libexec/nut/solis -D -a lobos -u root Network UPS Tools - M...

...red by OS. Can I configure nut to shut down a few minutes earlier? battery.charge: 93 battery.runtime: 1693 battery.voltage: 12.71 device.mfr: Eaton device.model: PW5115 500i device.serial: XcensoredX device.type: ups driver.name: bcmxcp driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyu0 driver.version: 2.6.1 driver.version.internal: 0.24 [current input/output] ups.beeper.status: enabled ups.firmware: Cont:01.00 Inve:10.04 ups.load: 20.4 ups.mfr: Eaton ups.model: PW5115 500i ups.power: 102 ups.power.nominal: 500 ups.serial: XcensoredX ups.status: OL

...my UPS. With ZERO 'send_pace' it work fine. > ________________________________________________ > > And at the end - part of my config (ups.conf), needed for correct working > and displayed data with my UPS. > > [sinapse] > ? ? ? ?driver = megatec > ? ? ? ?port = /dev/ttyu0 > ? ? ? ?desc = "Sinapse 6000" > ? ? ? ?sendpace=10 ? ? ? ? ? ? # or less, but not more 10 > ? ? ? ?battvoltmult=108 ? ? ? ?# for same as on LCD-display on UPS device > ? ? ? ?battvolts=1.90:2.2400 > _____________________________________________________ > > RESULTS: &...

...6 "/usr/libexec/getty Pc" xterm on secure ttyv7 "/usr/libexec/getty Pc" xterm on secure ttyv8 "/usr/local/bin/xdm -nodaemon" xterm off secure # Serial terminals # The 'dialup' keyword identifies dialin lines to login, fingerd etc. ttyu0 "/usr/libexec/getty std.19200" vt320 on secure ttyu1 "/usr/libexec/getty std.9600" dialup off secure ttyu2 "/usr/libexec/getty std.9600" dialup off secure ttyu3 "/usr/libexec/getty std.9600" dialup off secure # Dumb console dcons "...

Hi, I'm having lots of difficulties with BCM5719, which is the default network card of HP Proliant DL 360 G8 servers. I can get a few ping replies before I get a couple of these: bge0: watchdog timeout -- resetting bge0: watchdog timeout -- resetting Then everything hangs. Can not log in using ssh.

Guys, I've heard about some absurd RAM requirements for 9.1, has anybody tested it? e.g. http://forums.freebsd.org/showthread.php?t=36314 -- View this message in context: http://freebsd.1045724.n5.nabble.com/9-1-minimal-ram-requirements-tp5771583.html Sent from the freebsd-stable mailing list archive at Nabble.com.

Two machines (NFS Server: running ZFS / Client: disk-less), both are running FreeBSD r253506. The NFS client starts to deadlock processes within a few hours. It usually gets worse from there on. The processes stay in "D" state. I haven't been able to reproduce it when I want it to happen. I only have to wait a few hours until the deadlocks occur when traffic to the client machine