FedoraThis forum is for the discussion of the Fedora Project.
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.
There is less than 24 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have S500OPSL server board with Fedora Core 5 installed. When FC5 startup progress bar is filled and it is time to show the login screen the video card stops receiving signals (monitor's light goes red) if the mouse has been touched at any time before login screen. The same behaviour with/without installing GNOME (just with XWindows). The video card, keyboard and mouse are properly recognized. I went in step-by-step mode during boot and could not see any failure which could point to the problem.
Though there is no possibility to change the IRQ of the mouse port from BIOS but I changed the mouse from PS/2 to COM port. The result is the same. In addition I changed the IRQ of COM port still without success.
I noticed that sometimes when the mouse is plugged in the port, the disabling of the monitor (as well as keyboard and mouse) can happen even if I do not touch the mouse. But when I unplug the mouse from the mainboard I could always see a normal startup.
as a kernel argument but non of them helped the situation. Though after passing "pci=biosirq" I could see a normal startup on the first try but after issuing "shutdown -r 0" I faced the same hang-up situation.
I also was messing with BIOS PCI configuration and after disabling the Onboard NIC ROM the situation seems a bit better, that is most of the time I can see a normal login screen (with moving the mouse during boot), though sometimes it can again hang.
How could I disable the mouse PS/2 IRQ ? Do I need to configure the kernel source and recompile it ? or there exists an easier solution ?
I wished to understand this mouse problem as this could relate to some hardware problem. As I can understand this is more a Fedora bug than a hardware problem. As far as this server is going to be used as a cluster node, the mouse support will hardly be needed in any case. So at the time being I will admit that in text console mode the hardware is working fine.
I already set the latest available update into the BIOS and the ACPI Exception is still showing up. I hope this problem will not noticeably affect the overall performance.