similar to: Help with writing a udev rule

I have installed two 4-port serial cards (http://www.startech.com/ Product/ItemDetail.aspx?productid=PCI4S550&c=US) on a CentOS 4.4 system. The hardware appears to be recognized correctly, as kudzu added 2 entries to /etc/sysconfig/hwconf and lscpi shows both cards (output of lspci -vv for both cards included at the end of this email): # lspci 00:00.0 Host bridge: Intel Corporation

So, I made a mistake a bought four systems with the Intel Core i3 processors, without doing my homework to make sure that these systems actually supported VTd. Turns out there''s plenty of information out there indicating that the Core i3 processors do *not* support VTd. I was counting on VTd for two applications: Graphics Passthrough and passing through a PCIe 4-port serial card. Of

I am in the process of migrating from running CentOS 4.8 (32-bit) to CentOS 5.4 (64-bit) on my AMD Sempron(tm) Processor LE-1300 system (it is running CentOS 4.8 32-bit because the disk images are from a previous PIII system), and things are 'interesting' WRT how the Lava Computer mfg Inc Quattro-PCI card is being handled. lspci (on CentOS 4.8 32-bit) yields: 01:0a.0 Serial controller:

I have been investigating pci pass-through for virtualized guests and the documentation I have found seems to me to lack a certain consistency in its example. This may be due to my not understanding what it is trying to inform me. What I wish to do is to configure a pci multi-port serial i/o card for use by a single virtual host. I start by running lspci -v on the host to identify the serial

Hi Not entirely centos related but that what the boxes are running so here i go ;) 2 of our centos boxes run nagios for network monitoring and send email and paging alerts and are connected to standard phone lines using modems to send the pages. I'm looking for a way in the event of provider failure to login to these machines and so am looking at the ability to connect to the console over

Hi Guys, Has anyone successfully installed and ran the Dell Online Diagnostics for Centos 6.2? RHEL 6 is a listed as a supported OS, but it appears the install.sh shell script says it is unsupported. Any ideas? Thanks, Brad This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail

Unfortunately, almost all the Windows programs I want to run under Wine need to access the COM: ports, and I cannot get any of them to run. Typically, I get stuff like this ... fixme:comm:EscapeCommFunction16 no cid=0 found! fixme:comm:EscapeCommFunction16 no cid=0 found! err:comm:COMM16_ReadComplete async read failed 000003e3 fixme:comm:EscapeCommFunction16 no cid=3 found!

I am playing with a USR (us robotics) USB modem model 5637. in the past I used internal modems and had no issues. One this unit I plugged it in, dmesg says its recogized. I did "ln -s /dev/ttyACM0 /dev/ttyS4" this works. I then did "cu -l /dev/ttyS4" type "AT" and I get OK... looking good. When I "ATDT my number" I get a connection at 1200 baud (which I

Hi All I am connecting a ups via a usb to serial converter. Works fine, however when the converter is unplugged and plugged back in, udev creates another device e.g instead of ttyUSB0 it creates ttyUSB1. Here is the udev rule that I added to the top of the 025_nut-usbups.rules file in order to create a static symlink should udev decide to create the device as either ttyUSB0 or ttyUSB1.

On Sun, Mar 23, 2014 at 12:26:28PM +0000, Richard W.M. Jones wrote: > Secondly, we should be able to inspect all Linux guests, including > Tiny Core Linux, but it looks like in this case it is failing. This > is a bug. I had a look at how the Tiny Core Linux ISO is arranged. It loads the main operating system root partition as a single large initramfs, with optional modules loaded

Thanks for the help, with the apcsmart-old driver it works again! Didn't notice my UPS is now so "old" ;-) Here is the output of upsc with apcsmart-old driver: battery.alarm.threshold: 0 battery.charge: 100.0 battery.charge.restart: 00 battery.date: 11/22/06 battery.packs: 001 battery.packs.bad: 000 battery.runtime: 540 battery.runtime.low: 120 battery.voltage: 53.73

On Jun 13, 2013, at 7:14 AM, ML mail wrote: > I just upgraded to Network UPS Tools upsstats 2.6.4 on Debian wheezy and noticed that it does not show the battery runtime anymore, the field is simply empty. It used to work before with NUT 2.4.1. Does anyone know what could be wrong? > > I am using the apcsmart UPS driver. The apcsmart driver was overhauled, and in 2.6.x, the previous

Hello, I just upgraded to Network UPS Tools upsstats 2.6.4 on Debian wheezy and noticed that it does not show the battery runtime anymore, the field is simply empty. It used to work before with NUT 2.4.1. Does anyone know what could be wrong? I am using the apcsmart UPS driver. Thanks, M.L.

The Startech.com pci2s550 can not be remapped to ports 1-4 before the system boots. The company is not supporting linux serial ports as consoles 0-3 , thank you starTech.com. ----- Original Message ---- From: n schembr <nschembr at yahoo.com> To: SYSLINUX at zytor.com Sent: Thursday, November 9, 2006 4:58:50 PM Subject: [syslinux] Serial with syslinux. Can syslinux be upgraded to support

I've a line like this that creates /dev/pilot link in my local udev rules: BUS="usb", SYSFS{product}="Palm Handheld*", KERNEL="ttyUSB*[13579]", SYMLINK="pilot" And it seems to work fine for doing normal sync operation to Gnome Palm applet (well, not sure about that KERNEL parameter, however ttyUSB0 and ttyUSB1 look exactly the same, no other way to

I configured a domU to access to the physical serial port of the dom0 (/dev/ttyS0) typing this in the domU configuration file: irq = [ 4 ] ioports = [ "3f8-3ff" ] The domU starts without any error, but the serial port isn''t recognised. The /dev/ttyS0 device exists on the domU, and I blacklisted the serial_core, the 8250 and 8250_pnp modules on the dom0. What is the problem?

Hello, I have a strong suspicion that something is not working right on my el6 laptop. I have a usb 3g dongle that works fine on windows and ubuntu. It's one of those ZTE dual-personality devices (usb id 19d2:2000). When it's plugged in, it appears as usb storge device, then needs to be ejected, then it appears as usb modem with few serial ports. This is handled properly by udev on

The options -x -v gave me an error that no such option so I ruined it with —debug option. root@ny2proxd03:/var/lib/vz/images/100# virt-resize --expand /dev/sda3 vm-100-disk-1.qcow2 vm-100-disk-1.qcow2.resized --debug command line: virt-resize --expand /dev/sda3 vm-100-disk-1.qcow2 vm-100-disk-1.qcow2.resized --debug Examining vm-100-disk-1.qcow2 ... libguestfs: trace: add_drive

I've already read through bug 11811 (http://bugs.winehq.org/show_bug.cgi?id=11811) so I know a patch was offered about two years ago for Wine automatically recognizing the com* symlinks in ~/.wine/dosdevices. Is there any hope that this will be functional soon? I am trying a utility that needs to access the serial ports but there are none shown available in its ports dialog. I do have

Hello, Has anybody got Centos to work with multi-port serial cards? Or does anybody have multi-port serial or fax cards to recommend? Thanks.