Fedora :: Configuration Of Event.d Serial Devices - Inittab Don't Work
Jul 30, 2009
I was using V9 and upgrade to V10 and now my logins in my inittab do not work. I realize that is file structure is outdated so I made individual run files for each of my serial devices under event.d ( such as TX0000 - rc....etc) - all this works but i need to manual type initctl start TX000o to get logon for my serial devices. I would so much like them to automatically start on bootup.
I know in windows xp there is a registry key and an entry in the Plug and Play log file as well as maybe an event id, that is produced when a device (say usb) is plugged in. My question is, besides /var/log/ (messages?) Is there any other location that that information is stored in?
I am hoping to be able to get an old serial-touchscreen to work with a usb/serial adapter. I had this touchscreen working some years ago on different hardware. I would like to hook it to the machine I am setting up as a multimedia host with mythtv among other things.
Following the instructions I left behind when I got this to work way back when does not work. See [URL] ....
This info is a work around to get the xserver to see the touchscreen. [URL] ....
I do know that the touchscreen works as I am able to get garbage on the screen as in the first part of my howto. But I have not had any success getting xorg to see it. I wish I had posted a copy of the xorg.conf at the time, but......
There is an issue with the current xserver in testing that I am hoping the next update (in unstable) will fix when it gets pushed to testing. That is that Code: Select all# X -configure fails with a segfault. So I am not able to generate the xorg.conf needed to get it to work. I was going to post a bugreport, that is when I found out there is an update in unstable, so I am waiting for it to get pushed at the moment.
Anyway I am hoping that I can link /dev/ttyUSB0 to /dev/tty0 and get it to work. I would like some kind of guess as to my chances of success before I go to all the work of getting the monitor hooked to the host.
I did a forum search and too much came up that was not the answer I was looking for. I have only Linux devices at work and I was wondering how do Linux Administrators connect to Cisco devices via serial console cable. Cisco recommends 'Hyper Terminal' which was a Windows add-on applications licensed to XP. I think Vista and 7 no longer have the license to use Hyper Terminal. Regardless I don't have any versions of Windows and would like to use a serial cable from Com port 1 to the console port on the device. I can't use SSH since some devices don't support SSH and or I have to do a password recovery.
i have the following challenge: i have a Bluetooth GPS device that i have connected to my linux notebook. but now i also want to use the same device (or better, GPS data stream) for my Navigation device (HP Ipaq with TomTom). make an serial port bluetooth service (sending) that my Navigation device can connect to. copy the incoming bluetooth serial port data stream to the outgoing bluetooth serial port.
i have already installed GPSD so i have the TCP port where the GPS data is available for everything on my notebook. but now i also want it to send it out through bluetooth.
1. is there someone out there who already did this?
2. how to make an bluetooth serial port service on Fedora 12?
3. how to copy a data stream from 1 device to the next device?
Is there any Linux software that allows accessing a pre-configured serial console via Browser using a java applet? I would like to access the serial management consoles of various hardware devices via browser.
Just migrated to stretch, and noticed we're not using acpid anymore. Had couple of scripts at /etc/acpi/events listening for some events. What would be the alternative with systemd?
I know that this not a Slackware question, but since Slackware 13.1 has XFCE 4.6.2 in its standard installation I just ask here. I have a problem with the event sounds in XFCE 4.6.2 on Debian Sid. I already have a thread about this problem here, and couldn't solve it till now. I need to know if this issue is related to Debian or to XFCE, before I ask at the XFCE mailing list. So just one simple question: Has any one of you that is using XFCE got the event sounds to work?
i have a HP MSA 2312fc SAN with 2 LUNs configured. The first LUN (LUN ID 1) is correctly connected to the system, but when i connect the second LUN (LUN ID 30), i find in the syslog this message: multipathd: 8:64: size 6835937472, expected 5267578112. Discard
Here is the multipath.conf
[Code]....
So I correctly see the two luns, but multipath doesn't create the relative devices. Under /dev/mapper I see: control mpath0 mpath0-part1 mpath0-part1 is the first lun, the one I mounted in a directory under filesystem. I can't find the device for the second lun
I'm having trouble getting my wifi devices to work on my 128bit WEP network. I have a new Thinkpad T400, with an internal Intel PRO/Wireless 5100 AGN. I also have some cardbus cards: a Lucent ORiNOCO Gold, a Linksys Wireless-G, and a TRENDnet TEW-421PC. I have them set up as interfaces eth2, eth1, and eth3. (The TRENDnet isn't recognised as a network card at all, so no interface for it.) I have installed the latest firmware for the Linksys card.
The /etc/sysconfig/network-scripts/ifcfg-* files are virtually identical for all of them, differing only in the HWADDR and DEVICE lines. So here's the behaviour:
1. The Lucent card comes up just fine. 2. The internal 5100AGN and the Linksys cards won't come up, and watching with iwconfig shows that they're either associated with my AP OR they've got an encryption key set -- but not both. 3. When trying to bring up the 5100AGN, I get the following messages:
iwlagn: index 0 not used in uCode key table iwlagn: index 3 not used in uCode key table
/var/log/messages shows DHCPDISCOVER requests being sent, but they're bound to fail since the association with the AP with WEP isn't being completed. And yes, the ifcfg-* files really *are* identical except for the DEVICE and HWADDR lines. The /etc/udev/rules.d/70-persistent-net.rules file correctly maps the interfaces to the MAC addresses. So why does my antique ORiNOCO card work and thew newer ones fail? How can I track down what's being done wrong/not being done?
I've updated a Fedora Core 3 server to Fedora 11. The old FC3 had an external modem attached for when we felt like dialing in for a ppp connection. I've replicated login.config, mgetty.config and dialin.config from the old server and had to put a RS232-to-USB adapter on the modem. I've test connected to the server and everything look fine. I'm have a difficult time starting the getty session from inittab.
In Fedora 8 File: /etc/inittab contained S0:2345:respawn:/usr/sbin/faxgetty ttyS0 S1:2345:respawn:/sbin/vgetty ttyS1 In Fedora 13 Created folder: /etc/event.d Created files: /etc/event.d/ttyS0 [Code]....
Neither faxgetty or vgetty start on reboot or changing runlevel. How do you implement the equivalent of the old inittab function?
I'm using Fedora 15. For some reason, my computer is booting up graphically. I do not have video drivers for a graphical setup apparently now that Gnome is getting more advanced, so I really need to restore to a CLI. I see /etc/inittab is now deprecated thanks to systemd. The instructions say the following:
Code: # Ctrl-Alt-Delete is handled by /etc/systemd/system/ctrl-alt-del.target # systemd uses 'targets' instead of runlevels. By default, there are two main targets: # multi-user.target: analogous to runlevel 3 # graphical.target: analogous to runlevel 5 To set a default target, run: # ln -s /lib/systemd/system/<target name>.target /etc/systemd/system/default.target
And that's exactly what I have set up! Code: [root@server system]# pwd /etc/systemd/system [root@server system]# ls -la total 20 lrwxrwxrwx 1 root root 37 May 31 10:41 default.target -> /lib/systemd/system/multi-user.target
Why is this machine starting up graphically? I even removed the symlink and recreated it... but that obviously isn't the issue here.
I have been tol that for debugging purposes it is often useful to have a serial connection to a computer. I have some diskless workstations thats freezes during boot. I guess X has someting to do with this, but I'm not sure. Since the workstations are diskless, syslog is not stored locally so I cant se what is happening after the NiC stops working. When the worstation freezes, screen is going black, all lights on the keyboard turns on, lights on NiC is going black. It is not possible to ping the workstation.
I have a minilinux that I being working on, the problem now is that the serial ports doesn't seem to work (I have 4 serial ports).They don't write or read.
I run the command setserial g /dev/ttySx and it says that his IRQ are 3 or 4 (3 for ttyS0 and ttyS2 , 4 for ttyS1 and ttyS4)�but when I run the command: dmesg | grep ttyS the IRQ�s are 0 for ALL my serial ports� could be this the reason why my serial ports aren�t working right??? And if it is how can I solve the problem??
I'm using the serial port of a device to communicate with a hardware. (that can assume some different configurations of baud rate, data bits, etc.) Well, I can obtain that configuration, but I'm not certain in how to apply them to the serial. I'm using the struct termios to do that. I did some search, and found how to configure the baud rate and data bits. I'm doing this:
[Code]....
how I set the stop bits (1, 1.5 or 2 bits), the parity (even, odd, none, mark or space) and the flow control (hardware, software, none or xon/xoff)?
i need a usb to rs-232 converter to get into the console port i have an aten uc-232a converter and i have downloaded a .gz file called uplcom.4freebsd.gz i have unpacked it but i do not know what to do from here could some one please help i need to do some practice for the external icnd 2 exam and i have left it to the last minute as per usual.
I tried my COM mouse KM-203S on Windows, it works out of the box. Now i want to make it work on linux. But the problem is that mdetect doesn't recognize it, and whatever protocol i select in inputattach, the cursor jumps unpredictably when i move the mouse. How can i get the parameters for this mouse - maybe baudrate, etc.? Or maybe i'm doing something totally wrong?Here's mdetect output (i moved the mouse while mdetect was working) on 300 8N1 mode (set by minicom):
I installed ubuntu on a relative's computer but on the last moment, before the "restarting now" the screen began to spam this message. After this everytime the system logs on after 3~10 seconds the graphic interface freezes, so i entered the TTY1 before that, but again the message "serial8250 too much work for irq19" began to spam and obviously this is the cause of the problem
info: pentium dual core 2GB ram HDD 300GB ubuntu 10.04 32-bits what is thiis and how to fix it??
I had a web server running from a Windows 7 computer and recently moved everything to an Ubuntu server. All is set up and running smoothly. I do have one page that actually interfaces with the serial port. The only thing I do with it is to set the DTR pin to "true" which applies +12v to the pin. This activates a relay. It is very basic and simple. After moving everything to Linux, this page will no longer work. I knew this would happen. I know the page had code in it to call out "Com1" which would change to "ttyS0". It also had "set_serDTR(True);" in the code. I can't figure out how to get PHP to control the DTR pin on a Linux serial port.
With /usr/bin/canberra-gtk-play set to --id='desktop-login' in the startup Applications dialog one expects a sound to play at login. This is not the case with fedora 12. I set the variable to --file=/home/me/sounds/myloginsound and I got sound.
I'm curious as to why the event id failed. I suspect that id was not linked/associated with any sound before fedora 12 was released. How does one troubleshoot sound event ids and their associated sounds in f12.
I'd like to get audio when I log out as well. I recall seeing a dialog box with events and associated sounds in f11 (or was it f10?) .... I don't see it in f12
1. Does anyone know which package adds that functionality?
2. In the absence of a GUI approach, how can this be achieved (with the terminal)?
I'm trying to assign pci devices to pci-stub at boot before any of the kernel drivers can access it. I've successfully managed to do this on a Ubuntu system but I cannot get it to work on Debian. I've set pci-stub to load as a module in /etc/modules. I've then tried both these methods:
Add pci_stub ids=8086:100f to /etc/initramfs-tools/modulesSet GRUB_CMDLINE_LINUX_DEFAULT="pci_stub.ids=8086:100f" in /etc/default/grub.
Both give the same result after updating grub/initramfs and a reboot: when I check "dmesg | grep pci-stub" I get:
The actual device id's are not claimed by stub. Same for lspci -v which shows that the devices are still using the kernel drivers.Again, this configuration works on Ubuntu. Also issuing the following commands successfully assigns one of the devices to pci-stub but I need it to work on boot before the kernel drivers load:
I add one serical card which is extended to 4 serial ports to my host, but in centos 5.4, only 3 (In my machine, is ttyS1, ttyS2 and ttyS3,ttyS0 is another serial port) of my host can be used, and /dev/ttyS4 doesn't work.
$ sudo cat /dev/ttyS4 cat: /dev/ttyS4: No such device or address