Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello everyone!!!
I'm having a problem...After installing Fedora Core 3 on a HP machine, i installed an Equinox SST serial adapter. Then downloaded the drivers from Equinox and installed them.So far so good..
The problem is that most of the times when the machine is turned on , i get this error message:
init "q1" respawning too fast.Disabled for 5 minutes
In /etc/innitab the q1 is the first port of the Equinox.
The result of this error is that this port stops functioning...
Sometimes , when i reboot the machine the error does not appear, but most of the times, it does..
Any suggestions????
The problem is that the daemon started by init terminates quickly.
So first I'd take it out of inittab, and start it by hand for debugging.
Second, you must try to find its log files in order to determine the cause why it terminates right away. Starting it in foreground from a shell might also print some interesting error messages.
Thanx for replying...
The fact is that for the past 3-4 days, the problem has disappeared...!!!!!!
The thing is that in that port , i was going to attach a WinXP machine which was planned to communicate with the linux HP machine.
After connecting them together, the problem stopped.
So , my conclusion is that inittab (which is set to "respawn" for that port) expected to communicate with something. After not finding anything it was disabling the port...( i don't think that this is the way it should behave, though---at least RH8 wasn't behaving like that...)
I can't find any other logical explanation....
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.