USB to RS232 Terminal Emulator

As part of my job, I have to connect to equipment which uses an RS-232 interface. Since the PowerBook doesn't have a serial port which I can use to connect, I have available to me a USB-to-RS232 adapter. However, how do I establish this connection? On the Windoze laptops I can use HyperTerminal to establish the connection through the "COM" port, but is there a similar native application to the Mac or a recommended one? Can "Terminal" perform this function, as a VT100 Emulator? I've downloaded Soundforge's iTerm, but it just seems to be the same thing as "Terminal". Any suggestions?

A simple terminal emulator application that you can use is zterm.

Similar Messages

USB to RS232 converter

I would like to run a terminal emulator (eg. minicom) on my Arch box to look into my Netgear DM111P router.
I have the 3.3v TTL to RS232 converter already, but my IBM Thinkpad T40 does not have any (DB9) serial ports.
I was wondering if I could use the USB port instead with a RS232 to USB converter cable like this one:
http://www.amazon.co.uk/USB-RS232-Conve … B00077DJIQ
Can anyone tell me if this will work or what my other options are?

If I read you correctly, you're saying that the physical connection to the microcontroller is (DB9) serial, while the physical connection to your Arch box is USB and that you're running minicom on your Arch box to read the output from (and send input to) the microcontroller. Have I got that right? I'm new to this stuff, as you can tell, and I find it pretty confusing so I just wanted to clarify.
Could you suggest some serial-USB hardware to me as I've got to buy mine and I'd like to get something I know will work?

Controlling the Thermotron 7800 going USB to RS232.

     I'm very new to LabVIEW so I apologize if this is a quick fix I haven't stumbled across. My goal is to control my Thermotron 7800 which has an RS232 interface with a machine that only has USB. I'm using the manufacturer's LabVIEW drivers with LabVIEW 8.2.1. I've mass compiled them per instructions so they'll work with my 8.2 as they were written for LabVIEW 7.1. I've connected and used a 3rd party USB / RS232 converter with other hardware to this machine so I know that's not the issue and I can get the LabVIEW driver to recognize what port I'm connected to but I know no data is transferring across the cable as the indicator LED is not flashing and all I can get is a time out error.
     Anyone tried this before?

Hi,
I have a few questions/suggestions regarding your system.
1.     When installing the USB to rs232 convertor did you create a driver using the Driver Development Wizard? The following link will help you create an inf file to ensure proper communication with the instrument.
http://zone.ni.com/devzone/cda/tut/p/id/4478
2.     Use the following link to try a loopback test to verify the usb-rs232 hardware is operating correctly.
http://digital.ni.com/public.nsf/allkb/E22DA85E97818DE78625678C0069BFC9?OpenDocument
3.     Verify with the Thermotron manual that all the serial settings (BAUD rate, Parity, Start and Termination characters) are correct, like falkpl suggested.
4.     Try communicating to the instrument using a VISA test panel in Measurement and Automation Explorer. The VISA test panel can be accessed by right clicking on COM1 from Devices and Interfaces>>Serial & Parallel. The test panel allows the user to test basic serial write/reads without writing any code.
Regards,
Andy L.
Applications Engineer
National Instruments

Xmonad - Can't start any terminal emulator (xterm,urxvt,etc)

Hi,
I've recently installed Arch Linux in Virtualbox-OSE and also installed xmonad. It took me a while to get it running. It is all working fine and I can start all kinds of applications with MOD+Shift+P, but the only thing I can't do is start a terminal emulator such as xterm or urxvt. Neither with MOD+Shift+P and MOD+Shift+Return. When I do this I see a window flashing and I think it is the program I am trying to start but it is closing right after the startup.
Does anybody recognize this problem or know how to fix it?
Thanks,
Webfp

lifeafter2am wrote:Please post your xmoand.hs file and your xorg log.
my xmonad.hs
import XMonad
import XMonad.Util.Replace
import XMonad.Hooks.EwmhDesktops
main = xmonad $ ewmh defaultConfig
{ terminal = "urxvt"
, modMask = mod4Mask
, borderWidth = 0
xorg log
[ 174.789]
X.Org X Server 1.11.3
Release Date: 2011-12-16
[ 174.790] X Protocol Version 11, Revision 0
[ 174.791] Build Operating System: Linux 3.1.5-1-ARCH i686
[ 174.791] Current Operating System: Linux Laptop-Frank 3.1.8-1-ARCH #1 SMP PREEMPT Sat Jan 7 08:03:08 UTC 2012 i686
[ 174.792] Kernel command line: root=/dev/disk/by-uuid/1b11e5e6-5760-4dbb-9d54-0c982c0a37a4 ro
[ 174.794] Build Date: 17 December 2011 09:38:27AM
[ 174.794]
[ 174.795] Current version of pixman: 0.24.0
[ 174.795] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 174.796] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 174.801] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jan 11 16:17:09 2012
[ 174.883] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 174.928] (==) No Layout section. Using the first Screen section.
[ 174.928] (==) No screen section available. Using defaults.
[ 174.928] (**) |-->Screen "Default Screen Section" (0)
[ 174.928] (**) | |-->Monitor "<default monitor>"
[ 174.954] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 174.955] (==) Automatically adding devices
[ 174.955] (==) Automatically enabling devices
[ 175.021] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 175.021] Entry deleted from font path.
[ 175.057] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 175.057] Entry deleted from font path.
[ 175.057] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 175.059] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 175.059] Entry deleted from font path.
[ 175.059] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 175.059] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 175.059] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 175.060] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 175.072] (II) Loader magic: 0x8228580
[ 175.073] (II) Module ABI versions:
[ 175.073] X.Org ANSI C Emulation: 0.4
[ 175.073] X.Org Video Driver: 11.0
[ 175.073] X.Org XInput driver : 13.0
[ 175.073] X.Org Server Extension : 6.0
[ 175.078] (--) PCI:*(0:0:2:0) 80ee:beef:0000:0000 rev 0, Mem @ 0xe0000000/16777216
[ 175.079] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 175.079] (II) LoadModule: "extmod"
[ 175.104] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 175.136] (II) Module extmod: vendor="X.Org Foundation"
[ 175.136] compiled for 1.11.3, module version = 1.0.0
[ 175.136] Module class: X.Org Server Extension
[ 175.137] ABI class: X.Org Server Extension, version 6.0
[ 175.137] (II) Loading extension MIT-SCREEN-SAVER
[ 175.137] (II) Loading extension XFree86-VidModeExtension
[ 175.137] (II) Loading extension XFree86-DGA
[ 175.138] (II) Loading extension DPMS
[ 175.138] (II) Loading extension XVideo
[ 175.138] (II) Loading extension XVideo-MotionCompensation
[ 175.138] (II) Loading extension X-Resource
[ 175.139] (II) LoadModule: "dbe"
[ 175.142] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 175.146] (II) Module dbe: vendor="X.Org Foundation"
[ 175.146] compiled for 1.11.3, module version = 1.0.0
[ 175.146] Module class: X.Org Server Extension
[ 175.146] ABI class: X.Org Server Extension, version 6.0
[ 175.146] (II) Loading extension DOUBLE-BUFFER
[ 175.146] (II) LoadModule: "glx"
[ 175.147] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 175.166] (II) Module glx: vendor="X.Org Foundation"
[ 175.166] compiled for 1.11.3, module version = 1.0.0
[ 175.166] ABI class: X.Org Server Extension, version 6.0
[ 175.166] (==) AIGLX enabled
[ 175.166] (II) Loading extension GLX
[ 175.167] (II) LoadModule: "record"
[ 175.169] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 175.172] (II) Module record: vendor="X.Org Foundation"
[ 175.173] compiled for 1.11.3, module version = 1.13.0
[ 175.173] Module class: X.Org Server Extension
[ 175.173] ABI class: X.Org Server Extension, version 6.0
[ 175.173] (II) Loading extension RECORD
[ 175.173] (II) LoadModule: "dri"
[ 175.174] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 175.205] (II) Module dri: vendor="X.Org Foundation"
[ 175.205] compiled for 1.11.3, module version = 1.0.0
[ 175.205] ABI class: X.Org Server Extension, version 6.0
[ 175.205] (II) Loading extension XFree86-DRI
[ 175.205] (II) LoadModule: "dri2"
[ 175.207] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 175.210] (II) Module dri2: vendor="X.Org Foundation"
[ 175.210] compiled for 1.11.3, module version = 1.2.0
[ 175.210] ABI class: X.Org Server Extension, version 6.0
[ 175.210] (II) Loading extension DRI2
[ 175.211] (==) Matched vboxvideo as autoconfigured driver 0
[ 175.211] (==) Matched vesa as autoconfigured driver 1
[ 175.211] (==) Matched fbdev as autoconfigured driver 2
[ 175.211] (==) Assigned the driver to the xf86ConfigLayout
[ 175.211] (II) LoadModule: "vboxvideo"
[ 175.247] (II) Loading /usr/lib/xorg/modules/drivers/vboxvideo.so
[ 175.265] (II) Module vboxvideo: vendor="Oracle Corporation"
[ 175.266] compiled for 1.5.99.901, module version = 1.0.1
[ 175.266] Module class: X.Org Video Driver
[ 175.266] ABI class: X.Org Video Driver, version 11.0
[ 175.266] (**) Load address of symbol "VBOXVIDEO" is 0xb7396420
[ 175.266] (II) LoadModule: "vesa"
[ 175.268] (WW) Warning, couldn't open module vesa
[ 175.268] (II) UnloadModule: "vesa"
[ 175.269] (II) Unloading vesa
[ 175.269] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 175.269] (II) LoadModule: "fbdev"
[ 175.271] (WW) Warning, couldn't open module fbdev
[ 175.271] (II) UnloadModule: "fbdev"
[ 175.271] (II) Unloading fbdev
[ 175.272] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 175.272] (II) VBoxVideo: guest driver for VirtualBox: vbox
[ 175.273] (--) using VT number 7
[ 175.301] (II) Loading /usr/lib/xorg/modules/drivers/vboxvideo.so
[ 175.311] (II) VBoxVideo(0): VirtualBox guest additions video driver version 4.1.8_OSE
[ 175.341] (II) Loading sub module "ramdac"
[ 175.341] (II) LoadModule: "ramdac"
[ 175.342] (II) Module "ramdac" already built-in
[ 175.342] (II) Loading sub module "fb"
[ 175.342] (II) LoadModule: "fb"
[ 175.344] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 175.361] (II) Module fb: vendor="X.Org Foundation"
[ 175.361] compiled for 1.11.3, module version = 1.0.0
[ 175.362] ABI class: X.Org ANSI C Emulation, version 0.4
[ 175.362] (II) Loading sub module "shadowfb"
[ 175.362] (II) LoadModule: "shadowfb"
[ 175.370] (II) Loading /usr/lib/xorg/modules/libshadowfb.so
[ 175.378] (II) Module shadowfb: vendor="X.Org Foundation"
[ 175.378] compiled for 1.11.3, module version = 1.0.0
[ 175.379] ABI class: X.Org ANSI C Emulation, version 0.4
[ 175.379] (II) Loading sub module "vgahw"
[ 175.379] (II) LoadModule: "vgahw"
[ 175.379] (II) Loading /usr/lib/xorg/modules/libvgahw.so
[ 175.383] (II) Module vgahw: vendor="X.Org Foundation"
[ 175.383] compiled for 1.11.3, module version = 0.1.0
[ 175.383] ABI class: X.Org Video Driver, version 11.0
[ 175.383] (II) Loading sub module "dri"
[ 175.383] (II) LoadModule: "dri"
[ 175.384] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 175.384] (II) Module dri: vendor="X.Org Foundation"
[ 175.384] compiled for 1.11.3, module version = 1.0.0
[ 175.384] ABI class: X.Org Server Extension, version 6.0
[ 175.384] (II) VBoxVideo(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 175.385] (==) VBoxVideo(0): Depth 24, (--) framebuffer bpp 32
[ 175.385] (--) VBoxVideo(0): Virtual size is 32000x32000 (pitch 32000)
[ 175.385] (**) VBoxVideo(0): Built-in mode "VBoxInitialMode": 47.8 MHz (scaled from 0.0 MHz), 46.4 kHz, 60.0 Hz
[ 175.385] (II) VBoxVideo(0): Modeline "VBoxInitialMode"x0.0 47.83 1024 1026 1028 1030 768 770 772 774 (46.4 kHz)
[ 175.385] (**) VBoxVideo(0): Built-in mode "VBoxDynamicMode": 47.8 MHz (scaled from 0.0 MHz), 46.4 kHz, 60.0 Hz
[ 175.385] (II) VBoxVideo(0): Modeline "VBoxDynamicMode"x0.0 47.83 1024 1026 1028 1030 768 770 772 774 (46.4 kHz)
[ 175.385] (**) VBoxVideo(0): Built-in mode "VBoxDynamicMode": 47.8 MHz (scaled from 0.0 MHz), 46.4 kHz, 60.0 Hz
[ 175.386] (II) VBoxVideo(0): Modeline "VBoxDynamicMode"x0.0 47.83 1024 1026 1028 1030 768 770 772 774 (46.4 kHz)
[ 175.386] (**) VBoxVideo(0): Built-in mode "VBox-1024x768": 47.8 MHz (scaled from 0.0 MHz), 46.4 kHz, 60.0 Hz
[ 175.386] (II) VBoxVideo(0): Modeline "VBox-1024x768"x0.0 47.83 1024 1026 1028 1030 768 770 772 774 (46.4 kHz)
[ 175.386] (**) VBoxVideo(0): Built-in mode "VBox-800x600": 29.3 MHz (scaled from 0.0 MHz), 36.4 kHz, 60.0 Hz
[ 175.386] (II) VBoxVideo(0): Modeline "VBox-800x600"x0.0 29.31 800 802 804 806 600 602 604 606 (36.4 kHz)
[ 175.386] (**) VBoxVideo(0): Built-in mode "VBox-640x480": 18.8 MHz (scaled from 0.0 MHz), 29.2 kHz, 60.0 Hz
[ 175.386] (II) VBoxVideo(0): Modeline "VBox-640x480"x0.0 18.84 640 642 644 646 480 482 484 486 (29.2 kHz)
[ 175.389] (II) VBoxVideo(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
[ 175.389] (==) VBoxVideo(0): RGB weight 888
[ 175.389] (==) VBoxVideo(0): Default visual is TrueColor
[ 175.389] (==) VBoxVideo(0): Using gamma correction (1.0, 1.0, 1.0)
[ 175.390] (==) VBoxVideo(0): DPI set to (96, 96)
[ 175.390] (--) Depth 24 pixmap format is 32 bpp
[ 175.820] drmOpenDevice: node name is /dev/dri/card0
[ 175.821] drmOpenDevice: open result is 13, (OK)
[ 175.828] drmOpenDevice: node name is /dev/dri/card0
[ 175.829] drmOpenDevice: open result is 13, (OK)
[ 175.829] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
[ 175.829] drmOpenDevice: node name is /dev/dri/card0
[ 175.829] drmOpenDevice: open result is 13, (OK)
[ 175.829] drmOpenByBusid: drmOpenMinor returns 13
[ 175.829] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[ 175.830] (II) [drm] DRM interface version 1.4
[ 175.830] (II) [drm] DRM open master succeeded.
[ 175.830] (II) VBoxVideo(0): [drm] Using the DRM lock SAREA also for drawables.
[ 175.830] (II) VBoxVideo(0): [drm] framebuffer handle = 0xe0000000
[ 175.831] (II) VBoxVideo(0): [drm] added 1 reserved context for kernel
[ 175.831] (II) VBoxVideo(0): X context handle = 0x1
[ 175.835] (II) VBoxVideo(0): [drm] installed DRM signal handler
[ 175.836] (II) VBoxVideo(0): visual configurations initialized
[ 175.845] (II) VBoxVideo(0): Requested monitor count: 1
[ 175.845] (II) VBoxVideo(0): Output VBOX0 has no monitor section
[ 175.845] (II) VBoxVideo(0): Output VBOX0 has no monitor section
[ 175.846] (II) VBoxVideo(0): EDID for output VBOX0
[ 175.846] (II) VBoxVideo(0): Manufacturer: VBX Model: 0 Serial#: 50332672
[ 175.846] (II) VBoxVideo(0): Year: 1990 Week: 1
[ 175.846] (II) VBoxVideo(0): EDID Version: 1.3
[ 175.846] (II) VBoxVideo(0): Digital Display Input
[ 175.846] (II) VBoxVideo(0): Indeterminate output size
[ 175.846] (II) VBoxVideo(0): Gamma: 2.20
[ 175.846] (II) VBoxVideo(0): DPMS capabilities: StandBy Suspend Off
[ 175.847] (II) VBoxVideo(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[ 175.847] (II) VBoxVideo(0): Default color space is primary color space
[ 175.847] (II) VBoxVideo(0): First detailed timing is preferred mode
[ 175.847] (II) VBoxVideo(0): redX: 0.640 redY: 0.330 greenX: 0.300 greenY: 0.600
[ 175.847] (II) VBoxVideo(0): blueX: 0.150 blueY: 0.060 whiteX: 0.312 whiteY: 0.329
[ 175.847] (II) VBoxVideo(0): Manufacturer's mask: 0
[ 175.847] (II) VBoxVideo(0): Supported detailed timing:
[ 175.847] (II) VBoxVideo(0): clock: 47.8 MHz Image Size: 0 x 0 mm
[ 175.847] (II) VBoxVideo(0): h_active: 1024 h_sync: 1026 h_sync_end 1028 h_blank_end 1030 h_border: 0
[ 175.848] (II) VBoxVideo(0): v_active: 768 v_sync: 770 v_sync_end 772 v_blanking: 774 v_border: 0
[ 175.848] (II) VBoxVideo(0): Ranges: V min: 0 V max: 200 Hz, H min: 0 H max: 200 kHz, PixClock max 1005 MHz
[ 175.848] (II) VBoxVideo(0): Monitor name: VBOX monitor
[ 175.848] (II) VBoxVideo(0): EDID (in hex):
[ 175.848] (II) VBoxVideo(0): 00ffffffffffff005858000000040003
[ 175.848] (II) VBoxVideo(0): 0100010380000078eeee91a3544c9926
[ 175.848] (II) VBoxVideo(0): 0f505400000001010101010101010101
[ 175.848] (II) VBoxVideo(0): 010101010101af120006400006300202
[ 175.848] (II) VBoxVideo(0): 2200000000000000000000fd0000c800
[ 175.848] (II) VBoxVideo(0): c864000a202020202020000000fc0056
[ 175.849] (II) VBoxVideo(0): 424f58206d6f6e69746f720a00000010
[ 175.849] (II) VBoxVideo(0): 000a20202020202020202020202000fb
[ 175.849] (II) VBoxVideo(0): EDID vendor "VBX", prod id 0
[ 175.849] (II) VBoxVideo(0): DDCModeFromDetailedTiming: 1024x768 Warning: We only handle separate sync.
[ 175.849] (II) VBoxVideo(0): Using hsync ranges from config file
[ 175.849] (II) VBoxVideo(0): Using vrefresh ranges from config file
[ 175.849] (II) VBoxVideo(0): Printing DDC gathered Modelines:
[ 175.850] (II) VBoxVideo(0): Modeline "1024x768"x0.0 47.83 1024 1026 1028 1030 768 770 772 774 -hsync -vsync (46.4 kHz)
[ 175.851] (II) VBoxVideo(0): Printing probed modes for output VBOX0
[ 175.851] (II) VBoxVideo(0): Modeline "1024x768"x60.0 47.83 1024 1026 1028 1030 768 770 772 774 (46.4 kHz)
[ 175.851] (II) VBoxVideo(0): Modeline "800x600"x60.0 29.31 800 802 804 806 600 602 604 606 (36.4 kHz)
[ 175.851] (II) VBoxVideo(0): Modeline "640x480"x60.0 18.84 640 642 644 646 480 482 484 486 (29.2 kHz)
[ 175.851] (II) VBoxVideo(0): Output VBOX0 connected
[ 175.852] (II) VBoxVideo(0): Using exact sizes for initial modes
[ 175.852] (II) VBoxVideo(0): Output VBOX0 using initial mode 1024x768
[ 175.852] (II) VBoxVideo(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 175.852] (II) VBoxVideo(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 175.856] (==) VBoxVideo(0): DPMS enabled
[ 175.857] (II) VBoxVideo(0): [DRI] installation complete
[ 175.857] (--) RandR disabled
[ 175.857] (II) Initializing built-in extension Generic Event Extension
[ 175.857] (II) Initializing built-in extension SHAPE
[ 175.857] (II) Initializing built-in extension MIT-SHM
[ 175.857] (II) Initializing built-in extension XInputExtension
[ 175.857] (II) Initializing built-in extension XTEST
[ 175.857] (II) Initializing built-in extension BIG-REQUESTS
[ 175.857] (II) Initializing built-in extension SYNC
[ 175.857] (II) Initializing built-in extension XKEYBOARD
[ 175.857] (II) Initializing built-in extension XC-MISC
[ 175.858] (II) Initializing built-in extension SECURITY
[ 175.858] (II) Initializing built-in extension XINERAMA
[ 175.858] (II) Initializing built-in extension XFIXES
[ 175.858] (II) Initializing built-in extension RENDER
[ 175.858] (II) Initializing built-in extension RANDR
[ 175.858] (II) Initializing built-in extension COMPOSITE
[ 175.858] (II) Initializing built-in extension DAMAGE
[ 175.887] (II) AIGLX: Screen 0 is not DRI2 capable
[ 175.887] drmOpenDevice: node name is /dev/dri/card0
[ 175.887] drmOpenDevice: open result is 14, (OK)
[ 175.888] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
[ 175.888] drmOpenDevice: node name is /dev/dri/card0
[ 175.888] drmOpenDevice: open result is 14, (OK)
[ 175.888] drmOpenByBusid: drmOpenMinor returns 14
[ 175.888] drmOpenByBusid: Interface 1.4 failed, trying 1.1
[ 175.888] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[ 176.017] (II) Next line is added to allow vboxvideo_drv.so to appear as whitelisted driver
[ 176.017] (II) The file referenced, is *NOT* loaded
[ 176.017] (II) Loading /usr/lib/xorg/modules/drivers//ati_drv.so
[ 176.017] (EE) AIGLX error: vboxvideo does not export required DRI extension
[ 176.019] (EE) AIGLX: reverting to software rendering
[ 176.437] (II) AIGLX: Loaded and initialized swrast
[ 176.437] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 176.442] (II) VBoxVideo(0): Setting screen physical size to 270 x 203
[ 176.899] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[ 176.899] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 176.899] (II) LoadModule: "evdev"
[ 176.901] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 176.935] (II) Module evdev: vendor="X.Org Foundation"
[ 176.935] compiled for 1.10.99.902, module version = 2.6.0
[ 176.935] Module class: X.Org XInput Driver
[ 176.935] ABI class: X.Org XInput driver, version 13.0
[ 176.935] (II) Using input driver 'evdev' for 'Power Button'
[ 176.935] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 176.935] (**) Power Button: always reports core events
[ 176.935] (**) Power Button: Device: "/dev/input/event3"
[ 176.936] (--) Power Button: Found keys
[ 176.936] (II) Power Button: Configuring as keyboard
[ 176.936] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3"
[ 176.936] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 176.936] (**) Option "xkb_rules" "evdev"
[ 176.936] (**) Option "xkb_model" "evdev"
[ 176.936] (**) Option "xkb_layout" "us"
[ 177.050] (II) config/udev: Adding input device Sleep Button (/dev/input/event4)
[ 177.050] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 177.050] (II) Using input driver 'evdev' for 'Sleep Button'
[ 177.050] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 177.050] (**) Sleep Button: always reports core events
[ 177.051] (**) Sleep Button: Device: "/dev/input/event4"
[ 177.051] (--) Sleep Button: Found keys
[ 177.051] (II) Sleep Button: Configuring as keyboard
[ 177.051] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSLPBN:00/input/input4/event4"
[ 177.051] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 7)
[ 177.051] (**) Option "xkb_rules" "evdev"
[ 177.051] (**) Option "xkb_model" "evdev"
[ 177.051] (**) Option "xkb_layout" "us"
[ 177.055] (II) config/udev: Adding input device VirtualBox USB Tablet (/dev/input/event1)
[ 177.055] (**) VirtualBox USB Tablet: Applying InputClass "evdev pointer catchall"
[ 177.055] (II) Using input driver 'evdev' for 'VirtualBox USB Tablet'
[ 177.055] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 177.055] (**) VirtualBox USB Tablet: always reports core events
[ 177.055] (**) VirtualBox USB Tablet: Device: "/dev/input/event1"
[ 177.056] (--) VirtualBox USB Tablet: Found 9 mouse buttons
[ 177.056] (--) VirtualBox USB Tablet: Found scroll wheel(s)
[ 177.056] (--) VirtualBox USB Tablet: Found relative axes
[ 177.056] (--) VirtualBox USB Tablet: Found absolute axes
[ 177.057] (--) VirtualBox USB Tablet: Found x and y absolute axes
[ 177.057] (II) VirtualBox USB Tablet: Configuring as mouse
[ 177.057] (II) VirtualBox USB Tablet: Adding scrollwheel support
[ 177.057] (**) VirtualBox USB Tablet: YAxisMapping: buttons 4 and 5
[ 177.057] (**) VirtualBox USB Tablet: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 177.057] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb1/1-1/1-1:1.0/input/input1/event1"
[ 177.057] (II) XINPUT: Adding extended input device "VirtualBox USB Tablet" (type: MOUSE, id 8)
[ 177.057] (EE) VirtualBox USB Tablet: failed to initialize for relative axes.
[ 177.058] (II) VirtualBox USB Tablet: initialized for absolute axes.
[ 177.058] (**) VirtualBox USB Tablet: (accel) keeping acceleration scheme 1
[ 177.058] (**) VirtualBox USB Tablet: (accel) acceleration profile 0
[ 177.058] (**) VirtualBox USB Tablet: (accel) acceleration factor: 2.000
[ 177.058] (**) VirtualBox USB Tablet: (accel) acceleration threshold: 4
[ 177.060] (II) config/udev: Adding input device VirtualBox USB Tablet (/dev/input/js0)
[ 177.060] (II) No input driver/identifier specified (ignoring)
[ 177.062] (II) config/udev: Adding input device VirtualBox USB Tablet (/dev/input/mouse0)
[ 177.063] (II) No input driver/identifier specified (ignoring)
[ 177.065] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 177.065] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 177.065] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 177.066] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 177.066] (**) AT Translated Set 2 keyboard: always reports core events
[ 177.066] (**) AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 177.066] (--) AT Translated Set 2 keyboard: Found keys
[ 177.066] (II) AT Translated Set 2 keyboard: Configuring as keyboard
[ 177.066] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 177.066] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
[ 177.066] (**) Option "xkb_rules" "evdev"
[ 177.067] (**) Option "xkb_model" "evdev"
[ 177.067] (**) Option "xkb_layout" "us"
[ 177.070] (II) config/udev: Adding input device ImExPS/2 Generic Explorer Mouse (/dev/input/event5)
[ 177.070] (**) ImExPS/2 Generic Explorer Mouse: Applying InputClass "evdev pointer catchall"
[ 177.070] (II) Using input driver 'evdev' for 'ImExPS/2 Generic Explorer Mouse'
[ 177.070] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 177.070] (**) ImExPS/2 Generic Explorer Mouse: always reports core events
[ 177.070] (**) ImExPS/2 Generic Explorer Mouse: Device: "/dev/input/event5"
[ 177.070] (--) ImExPS/2 Generic Explorer Mouse: Found 9 mouse buttons
[ 177.071] (--) ImExPS/2 Generic Explorer Mouse: Found scroll wheel(s)
[ 177.071] (--) ImExPS/2 Generic Explorer Mouse: Found relative axes
[ 177.071] (--) ImExPS/2 Generic Explorer Mouse: Found x and y relative axes
[ 177.071] (II) ImExPS/2 Generic Explorer Mouse: Configuring as mouse
[ 177.071] (II) ImExPS/2 Generic Explorer Mouse: Adding scrollwheel support
[ 177.071] (**) ImExPS/2 Generic Explorer Mouse: YAxisMapping: buttons 4 and 5
[ 177.071] (**) ImExPS/2 Generic Explorer Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 177.071] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input5/event5"
[ 177.071] (II) XINPUT: Adding extended input device "ImExPS/2 Generic Explorer Mouse" (type: MOUSE, id 10)
[ 177.072] (II) ImExPS/2 Generic Explorer Mouse: initialized for relative axes.
[ 177.072] (**) ImExPS/2 Generic Explorer Mouse: (accel) keeping acceleration scheme 1
[ 177.072] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration profile 0
[ 177.072] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration factor: 2.000
[ 177.072] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration threshold: 4
[ 177.074] (II) config/udev: Adding input device ImExPS/2 Generic Explorer Mouse (/dev/input/mouse1)
[ 177.074] (II) No input driver/identifier specified (ignoring)
[ 177.077] (II) config/udev: Adding input device PC Speaker (/dev/input/event6)
[ 177.078] (II) No input driver/identifier specified (ignoring)
[ 177.082] (II) config/udev: Adding input device VirtualBox mouse integration (/dev/input/event2)
[ 177.082] (**) VirtualBox mouse integration: Applying InputClass "evdev pointer catchall"
[ 177.082] (II) Using input driver 'evdev' for 'VirtualBox mouse integration'
[ 177.082] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 177.082] (**) VirtualBox mouse integration: always reports core events
[ 177.082] (**) VirtualBox mouse integration: Device: "/dev/input/event2"
[ 177.083] (--) VirtualBox mouse integration: Found 1 mouse buttons
[ 177.083] (--) VirtualBox mouse integration: Found absolute axes
[ 177.083] (--) VirtualBox mouse integration: Found x and y absolute axes
[ 177.083] (II) VirtualBox mouse integration: Configuring as mouse
[ 177.083] (**) VirtualBox mouse integration: YAxisMapping: buttons 4 and 5
[ 177.083] (**) VirtualBox mouse integration: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 177.084] (**) Option "config_info" "udev:/sys/devices/virtual/input/input2/event2"
[ 177.084] (II) XINPUT: Adding extended input device "VirtualBox mouse integration" (type: MOUSE, id 11)
[ 177.084] (II) VirtualBox mouse integration: initialized for absolute axes.
[ 177.084] (**) VirtualBox mouse integration: (accel) keeping acceleration scheme 1
[ 177.084] (**) VirtualBox mouse integration: (accel) acceleration profile 0
[ 177.084] (**) VirtualBox mouse integration: (accel) acceleration factor: 2.000
[ 177.084] (**) VirtualBox mouse integration: (accel) acceleration threshold: 4
[ 177.086] (II) config/udev: Adding input device VirtualBox mouse integration (/dev/input/js1)
[ 177.086] (II) No input driver/identifier specified (ignoring)
BTW it was a real hassle to find the content of those files when you do not have a terminal emulator to use.

Terminal emulator advice?

Coming from linux, I would use minicom to connect to hardware devices via usb->serial->device. What app is recommended for this on a Mac? I did try to install mini-com, but even after the xcode install, still failing the compile so I figure there is a better app to do just that.
Thanks

...just amazing there is no basic free emulator.
Macs have not had serial ports for about 10 years. If you needed to connect a serial device, you needed a 3rd party adaptor (and one would assume the adaptor manufacture would provide the needed software to use their device).
Mac OS X does provide a Terminal emulator, but it just emulates a terminal. It does not have code that talks to a serial port.
I guess you could just use various shell scripting tools to talk to the /dev/???? device. I remember back in my Tru64 UNIX days, there was a utility called 'tip' that was used when you wanted to talk to a serial port. I did not find 'tip' on the Mac, nor as part of MacPorts.org.
A Google search for "Mac OS X serial port utility" turned up:
<http://mac.rbytes.net/cat/mac/utilities/osx-serial-port-tool/>
<http://homepage.mac.com/chen/w7ay/Serial%20Tools/index.html>
There may be others.
You could also wonder over to VersionTracker.com and MacUpdates.com, which keep track of Mac OS X software.

Terminal emulation for OS X Server 10.5.8?

We use Xsan with 2 Xservers and 2 Promise arrays. Promise tells me I need to use a terminal emulator to get information from the arrays over a seril connection. The emulator has to emulate a VT100 or ANSI terminal. Neither Promise nor Apple Support would recommend a terminal emulator.
Does anyone have experience running a terminal emulator on an Xserve running OS X Server 10.5.8? Is there one you would recommed? Not recommend?
Thanks in advance.
Chuck

Last time I did this I used a USB to Serial adaptor on a MacBook Pro with ZTerm software.
See http://www.dalverson.com/zterm/
The XServe in theory has a built-in serial port but at the time I tried it, I could not get ZTerm to successfully communicate via it, the USB serial adaptor (this one - http://www.macwise.com/Keyspan.html ) worked fine.

[SOLVED] Terminal emulator that allows free resizing?

EDIT: Answered my own question; terminator allows per-pixel resizing if you disable window hinting in the preferences.
I have an annoyance with resizing terminal emulators. I use stacking WMs (xfwm4 on one setup, compiz standalone on another) but I usually like to tile my windows manually. I've enabled edge snapping in both of these WMs. However, whenever I'm resizing a terminal window, the snapping doesn't work because the terminal window can't be freely resized - I can only change the size of the window by one character's height/width. For example, if a terminal is open at 80x36, and I want to make it just a little bit wider to snap against the edge of another window, I can't because it won't let me resize the window between 80 and 81 characters.
I've tried xfce's terminal, gnome-terminal, lxterminal, xterm, urxvt, and st. Can someone direct me to a terminal emulator that will let me resize windows to whatever size I want, regardless of whether it is a discrete character size, or am I out of luck?
P.S. I've noticed that if I resize a window with wmctrl and issue the resize command twice, then xfce's terminal behaves the way it should. Can I replicate this behavior for resizing with the mouse?
Last edited by thorion (2012-10-19 05:14:41)

A terminal emulator and X Window GUI are different things. You can have a terminal emulator in a graphical desktop environment, but you cannot display GUI in a terminal.
Putty is just a SSH client and terminal emulator (VT) and can be used with X-forwarding to display remote GUI applications (Linux), provided you are have a X Window server installed and running on your local computer, e.g. Xming Server for Windows.
Perhaps you will find the free version of http://mobaxterm.mobatek.net/ useful. It is a single application based on Cygwin that allows you run GUI applications from your remote Linux system.
By far the best terminal emulator in terms of user interface and configuration options that I’m aware of is the Terminal App of MacOSX, which also automatically opens Xorg if you open a GUI application. And it provides the full set of terminal escape sequences. But if you are on Windows….
Alternatively, use VNC. You can run VNC in several modes, either to open an existing remote desktop connection, start a new desktop connection, or run a minimal X windows server, such as TWM that does not require you to install or run a graphical user desktop on your remote Linux server. If you are interested in VNC, perhaps check the following: https://community.oracle.com/thread/2456580. You can also tunnel VNC through SSH if your network firewall prevents communication.

Is there a terminal emulator with up- down output?

The idea just hit me but it's very hard to find something in search or on google (up and down are popular keywords...).
Here's my idea: the terminal I use (urxvt) and every other I heard of always outputs text sort of 'upwards'. Meaning: the prompt line is mostly on the bottom (and if you use a tiling wm like me it's mostly on the bottom of the screen), well except for new terminal windows of course.
I thought it would be cool if it could be on the top of the screen and the lines would be output towards the bottom of the window. Get it? If you would take a normal terminal window and reverse the lines order, this would be exactly what I need.
Quick example:
A normal terminal
[user@desktop]: ls -l
drwxr-xr-x 5 user user 4096 Jan 17 12:53 dir1
lrwxrwxrwx 1 user user 30 Dec 23 17:14 a-link
drwxr-xr-x 2 user user 4096 Feb 10 13:26 dir2
[user@desktop]: _
What I would like
[user@desktop]: _
drwxr-xr-x 5 user user 4096 Jan 17 12:53 dir1
lrwxrwxrwx 1 user user 30 Dec 23 17:14 a-link
drwxr-xr-x 2 user user 4096 Feb 10 13:26 dir2
[user@desktop]: ls -l
Get it? Top -> down! So the prompt always gravitates toward the top of the window (provided enough output of course)
So anyway, back to the question: is there a terminal emulator that can do it?
Last edited by kosmiciatakuja (2011-03-14 10:47:55)

lives2evil wrote:Interesting idea!
But no, as far as I know there's no such things.
Any if you think it a little further, it's a trouble some idea. You may not notice with a simple "ls" command but with something more complex trouble will pop up every where.
How about you try and think how exactly will you implemented this idea.
Could be fun (Tried it).
Heh yea, i just did the same and came to the same conclusions.

USB to RS232 Adapter and Driver Advise - Heeeeelllllllpppppp Please!!

Hi All,
Can someone please help me with an issue im having.
I currently have a hl-340 usb to rs232 adapter for me to be able to Console on to cisco equipment (as i am a network engineer).
I can not get this to work!! i have installed the pl2303 driver as recommended by the place who sold this to me on ebay which has not worked, i have looked around and saw the option of installing the keyspan for this product USA-19HS but with no joy.
I need to get this working ASAP or look to purchase a new one. I am based in the UK so if it is not possible to get this working then can you advise on what one will work?
I am a novice to the Mac so any assistance you can all give will be greatly received.
Thanks

Let's figure out what you have first. Plug in you RS-232 adapter. If the system has a driver that recognizes it, it should pop up a window about detecting a new network interface. If that happens, your USB device is recognized and should be working. If not, you may have the wrong driver loaded.
In any case, open the System Profiler application (click the Apple logo in the menu bar, then About This Mac, then More Info). When the app opens, click USB (under the Hardware heading) in the left window pane. This will reveal all detected USB buses, hubs, and devices. On my system, my RS-232 adapter shows up as USB-Serial Controller. Clicking on it shows these details in the bottom pane:
USB-Serial Controller:
Product ID: 0x4026
Vendor ID: 0x1453
Version: 3.00
Speed: Up to 12 Mb/sec
Manufacturer: Prolific Technology Inc.
Location ID: 0xfd323000
Current Available (mA): 500
Current Required (mA): 100
Your details may be different, especially the Product and Vendor ID. For the PL2303 driver to work, I think the important part is that the Manufacturer is Prolific Technology. If it's something else, you may need a different driver. Try to find your device, and reply back with its details.
With the adapter still connected, click Extensions (under the Software heading) in the left window pane. A list of all kernel extensions will be displayed. This will take a while.
On my system, with the driver that I recommended, the extension name is osx-pl2303. Clicking on it shows these details in the bottom pane:
osx-pl2303:
Version: 1.0.0d1
Last Modified: 05/27/06 11:49
Kind: Universal
Architectures: i386, ppc
64-Bit (Intel): No
Location: /System/Library/Extensions/osx-pl2303.kext
Kext Version: 1.0.0d1
Load Address: 0x3599e000
Valid: Yes
Authentic: Yes
Dependencies: Satisfied
If yours also displays this, then your device should be working. If so, then you'll need to figure out how to get your software to recognize it. Reply back with whatever details you find.

Terminal Emulation/TN5250 on a Blackberry

All -
I am looking for some software to do terminal emulation on the Blackberry. I used to use MobileSSH from Rove, but now that they have incorporated it into Mobile Admin, I can no longer purchase just MobileSSH and the cost has also rised about 3x-4x to $595 and I can't get justification for that amount of money.
I am wanting to connect to an AS/400 through MDS via TN5250 emulation. I will need function key access, special character input ability, and field exit key capability. Any suggestions anyone? Please let me know!!
Thanks,
Charlie
Blackberry Administrator
BES 4.1.6 MR1 with Lotus Domino 8.0.1
58 Users

HI and welcome to the forums!
http://www.my-install.com/prog/Network-Internet-Terminal-Telnet-Clients/36377/Mobile-SSH-for-BlackBe...
Idokorro Mobile. Shareware.
Thanks,
Please remember to resolve your thread. Put the check mark in the green box that contained your answer! Thanks
Message Edited by Bifocals on 11-11-2008 11:47 PM
Click Accept as Solution for posts that have solved your issue(s)!
Be sure to click Like! for those who have helped you.
Install BlackBerry Protect it's a free application designed to help find your lost BlackBerry smartphone, and keep the information on it secure.

Intall X3270 Terminal emulator on Solaris 10 x86

Hi! I'm trying to install IBM 3270 Terminal Emulator from source code on solaris 10 x86. I had some problems when I run ./configure but was PATH's configuration. Now I'm trying to run make but at certain moment the folowing erro return:
makeconv -d . -p icudt3l ibm-837_P100-2000.ucm
sh: makeconv: not found
*** Error code 1
make: Fatal error: Command failed for target `icudt3l_ibm-837_P100-2000.cnv'
I tried to find this 'makeconv' but I haven't found. Does anybody have some esperience with the instalation of X3270? Thank's a lot.

problem 1 is that it's looking for ../../s0.. Which I
managed to
fake out by creating the dir in the same mount
point.
Problem 2 is that it can't find .tmp_proto, which I
must
concur with. I can't find that on any of the b72 cd
images.
So, the setup_install_server fails.This seems to be the problem when you try to setup an install
server on a Solaris SPARC system for Solaris x86 clients, using
the Solaris 9 or Solaris 10/Express CD media.
There's a Solaris x86 UFS filesystem on slice 0 on the CD media,
and it's supposed to be mounted on the "s0" mount point,
otherwise setup_install_server won't work. On a Solaris x86 box,
vold mounts it automatically for you: /cdrom/cdrom0/s2 is the
mount point for the platform independant ISO9660 part of the CD
media, /cdrom/cdrom0/s0 is the UFS root filesystem.
Problem is that Solaris SPARC:
- does not understand Solaris x86 disk labels
- does not allow mounting x86 UFS filesystems
(and vice versa).
AFAIK, Solaris 9 DVD media does not have this problem. I
guess the same will be true when Solaris 10 DVD media is
available in a few months. On the DVD media there's enough
free space to include an extra copy of the files in the ISO9660
filesystem.

Using SecureCRT or other terminal emulator application for Telnet of LMS

Hi Everyone,
How to I set SecureCRT/Hyperterm or other terminal emulator as the one that will be use to telnet a device from Device Center or Topology Services?
Many thanks.

For Device Center, it depends on which browser you use. If it's Mozilla/Firefox, it can be as simple as modifying the Helper application in the Preferences. Or if it's IE 7 or 8, you could modify the registry setting for the telnet:// protocol (see this post https://supportforums.cisco.com/message/670709), or alternatively replace the Windows telnet.exe binary with a shortcut to SecureCRT if you don't mind using the latter all the time.
For Topo Service in Campus Manager, you need to create a campusmgr.properties file as described in http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_campus_manager/5.0/user/guide/cmugfull.pdf, and keep in mind of http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsa80409 that afflicts CM 4.0 and Windows 2003 and Windows XP clients.

Multimedia key issue in a terminal emulator

My keyboard has a few multimedia keys(XF86AudioRaiseVolume, etc.) and
they have been correctly recognized by X and have keycodes/keysyms. I
can get them work on most programs, but they are not recognized by
programs run inside a terminal emulator(urxvt or xterm, for example).
Specifically, I want to control my emms playlist via
XF86AudioPrev/XF86AudioNext. I have the key bindings in emacs start up
file and it actually works when emacs appears as a standalone X
window. But it fails when emacs is inside a terminal. it appears to
me that the terminal/shell never delivers these key strokes to any
processes spawned by them.
I searched for the keysym/keymap resources in urxvt/xterm but can't
quite catch the idea and don't even know if this helps.
Last edited by eirika (2009-09-15 02:50:23)

Response marked with
line 1 16
modem InOut
it says that, "line 2 does not support modem control"
- can you please try only one line at a time, that is:
line 1
modem inout
then try line 2 and so on and see if we see errors for specific lines only (which we can investigate further)
Then I typed:
(config)#line 0 17
(config-line)#modem InOut
it says, "line 0 does not support modem control. Now it doesn't talk about line 2, instead it says that line 0 does not support modem control.
This error is ok since line 0 is console and does not support modem control, mind you IOS spills out errors one after another so probably would have given error for line 2 next.
In here, the main problem is that, when I type:
(config)#line 1 16
(config-line)#no exec
and when I telnet, the router doesn't even prompt for anything. But when I again say, "exec" in line mode, then the router prompts me for the username.
Do you mean reverse telnet out of these lines? Not sure I understand what you are trying to do here.
A few things to check:
1. Is the router completely up, means its not in boot mode etc.
2. Are the IOS images different or same on the working vs non working 2511?
Thanks, Mak

How to put computer to sleep or reset USB bus from Terminal?

I'm using Missing Sync to connect a Windows Mobile PocketPC to my Mac for synchronizing data. Occasionally, as soon as I plug in the USB cable, the whole system gets hung. My mouse and keyboard don't work, but I can get into the system via SSH from another machine. Once I'm in, is there anything I can do that's more graceful than using the button on the front of the Mac to shut it off? For example, can I get it to sleep (and then wake up) from terminal? Maybe that will reset things. Or maybe there's a way to re-init the USB bus from terminal. Any suggestions? I hate shutting it off via the button - what's the better way, once it gets hosed like that?
Mike

There may be other processes you can kill instead (or in addition), but without
seeing more about the state of the machine it's hard to tell.
what information would you want to see about the state of the machine? Is there something in the console log that I can post? I'd like to be ready with all of the possible KILLs when this happens again... In general, what processes do I kill to reset stuff without a hard reset? Logging me out of the account is fine; a graceful software reboot is ok too - I just hate the cold shutdown from the power button.
Thanks!
Mike

[SOLVED] Tmux in terminal emulator having strange effect on X session

Hello. I've searched about and googled for this problem for a while, but to no avail. The problem is this:
When in an X session, in the Awesome WM, when I fire up a terminal emulator (so far I tried lxterminal, xterm, urxvt and lilyterm), the console (from before the X session) appears with the X startup messages and it's stuck that way. I'm still in the WM however and the mouse shows. I just can't see anything past that console screen. I can't see any error messages thereon either.
When not in Awesome (and X), tmux starts up fine, and also when in Awesome and I run
sudo tmux
in the terminal emulators.
I first encountered this some time ago, using just lilyterm, but then I tried running tmux in lxterminal instead and it worked fine. Now this always happens, no matter the terminal. Right before this incident, I was doing some experiments with running a detached tmux session on login. I tried executing in .bash_profile, .bashrc, .xinitrc and .config/awesome/rc.lua. Since this started happening at some point, I'm not sure when, I tried some different files. Now I have removed what I put in them but this behavior keeps occurring. I've tried to make sure the $TERM variable is set right inside and outside tmux for some of them and
set -g default-terminal "screen/screen-color256"
in the .tmux.conf.
I sync my config files between my laptop and desktop so they have the same behavior, except on the desktop the console screen flashes momentarily and then all GUI programs have disappeared from the screen, leaving just bare Awesome. I can then start some more GUI programs again. If I try to start tmux again in another terminal emulator. I get the "nested tmux sessions" message.
I don't know if it matters, but using screen instead works as intended. Anyway, any help is appreciated. My tmux.conf is really just
set -g default-terminal "screen"
at the moment.
Last edited by m73 (2013-07-22 12:06:03)

Tried the same in Openbox instead of Awesome and I get the same behavior. I also made a tmux session before starting X and attached it in the terminal emulator afterwards. That worked, but when I try to make a new window in that session with Ctrl-b C, the same thing happens. So this happens if I try to make new sessions or windows as the current user in an X session. Listing and killing sessions works as intended.

USB to RS232 Terminal Emulator

Similar Messages

Maybe you are looking for