compsol1993
asked on
Linux - KVM Install
Hello,
We are running Mandriva 2007 as a LAMP server. It has been working perfectly until now. We installed a new KVM for our server cluster. We were using a Trendnet 4-Port and we upgraded to a D-Link 8-port. All of the other (Windows 2003) servers work fine on the new KVM. The linux server is the only problem. When the keyboard and mouse are connected to linux box through the KVM, boot stops at "Starting HAL Daemon". At this point, the screen does not change at all but I have the ablity to type directly under "Starting HAL Daemon" as if it were a text editor. If I leave the machine idle for about 5 minutes, the screen goes black and then nothing I do will bring it back to the booting screen.
If I reconnect the keyboard and mouse directly to the server, it works fine.
Does anybody have any suggestions of what I can do to fix this?
Thanks
We are running Mandriva 2007 as a LAMP server. It has been working perfectly until now. We installed a new KVM for our server cluster. We were using a Trendnet 4-Port and we upgraded to a D-Link 8-port. All of the other (Windows 2003) servers work fine on the new KVM. The linux server is the only problem. When the keyboard and mouse are connected to linux box through the KVM, boot stops at "Starting HAL Daemon". At this point, the screen does not change at all but I have the ablity to type directly under "Starting HAL Daemon" as if it were a text editor. If I leave the machine idle for about 5 minutes, the screen goes black and then nothing I do will bring it back to the booting screen.
If I reconnect the keyboard and mouse directly to the server, it works fine.
Does anybody have any suggestions of what I can do to fix this?
Thanks
ASKER
One more bit of information, the keyboard works through the KVM. It is only the mouse that is causing this problem.
I've seen this before. Your KVM is somehow not keeping the signal alive when you switch away. Only solution I can think of is to get a better KVM switch. IMHO, anything that says "D-LINK" on it, does not belong in the enterprise server room.
ASKER
Ok, but in this case, I do not switch away. I set the KVM to the linux computer before I boot, then turn the linux box on. It takes about 20 seconds before it gets to "Starting HAL Daemon". At no time do I switch away.
Considering that, do you have any other ideas?
Thanks
Considering that, do you have any other ideas?
Thanks
is it USB or PS2? if it can use both, try using USB.
ASKER
Unfortunately it is only PS2. I've also tried a different mouse, it didn't make a difference. I also tried the KVM in both powered and un-powered mode. It did not make a difference.
I'd have to agree as regards D-Link I'm afraid. The 8-port Belkin KVM's are also complete toss.
We just invested in our first Raritan Dominion 32-port IP-KVM as part of our migration to the 21st century. To describe it as outstanding would be understatement. Still retains local access, but everything can be done through a browser.
We just invested in our first Raritan Dominion 32-port IP-KVM as part of our migration to the 21st century. To describe it as outstanding would be understatement. Still retains local access, but everything can be done through a browser.
ASKER
Thanks for the info. Considering that we know have the D-Link, and it is not feasible to return, do you have any suggestions for getting around the problem? What does it mean when it stops at "Starting HAL Daemon"?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
just as a lark, check to see if you have the mouse and keyboard cables swapped.
ASKER
I found the solution to this problem. When it was ejecting the CD drive that was the key. It needed drivers off of the original linux boot disk. It didn't give any message indicating that, but that is what it was looking for.
Also, just putting the disk in and waiting for the computer to do something did not work. The only way to get it to pull the driver off of the CD was to:
Boot the computer, wait until it starts to boot from the hard drive, immediately put the install disk in the drive, then when it gets to the "Starting HAL Daemon" it will quickly grab the driver and boot like normal.
Also, just putting the disk in and waiting for the computer to do something did not work. The only way to get it to pull the driver off of the CD was to:
Boot the computer, wait until it starts to boot from the hard drive, immediately put the install disk in the drive, then when it gets to the "Starting HAL Daemon" it will quickly grab the driver and boot like normal.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER