I have a Logitech wireless MX Duo that worked fine with FC3. I purchased this after I had installed and setup FC 3 and after playing around with the connects a few times it worked great.
Now I installed FC4 as a fresh install and everything worked during the Anaconda install, keyboard and mouse. When I reboot, nothing is recognised and I need to shutdown the PC by single push of the power button so that FC3 shuts down normally.
I have gone through the connect procedure numerous times but the mouse never works. I have the mouse and keyboard connected to the PS2 connectors directly (use a KVM also, but not at the moment). I do not want to use the USB connectors, even to get it going as I don't want to possibly be stuck using that.
USing Rescue I checked the xorg.conf file and everything seems fine in there when I compare to a different machine (different mouse & keboard through a KVM)
Any ideas on how to get things working?
On Sun, 2005-07-31 at 12:17 -0400, David Niemi wrote:
I have a Logitech wireless MX Duo that worked fine with FC3. I purchased this after I had installed and setup FC 3 and after playing around with the connects a few times it worked great.
Now I installed FC4 as a fresh install and everything worked during the Anaconda install, keyboard and mouse. When I reboot, nothing is recognised and I need to shutdown the PC by single push of the power button so that FC3 shuts down normally.
I have gone through the connect procedure numerous times but the mouse never works. I have the mouse and keyboard connected to the PS2 connectors directly (use a KVM also, but not at the moment). I do not want to use the USB connectors, even to get it going as I don't want to possibly be stuck using that.
USing Rescue I checked the xorg.conf file and everything seems fine in there when I compare to a different machine (different mouse & keboard through a KVM)
Any ideas on how to get things working?
I would use the USB connectors.
Can you use the keyboard to enter your computer's bios?
David Niemi wrote:
I have a Logitech wireless MX Duo that worked fine with FC3. I purchased this after I had installed and setup FC 3 and after playing around with the connects a few times it worked great.
Now I installed FC4 as a fresh install and everything worked during the Anaconda install, keyboard and mouse. When I reboot, nothing is recognised and I need to shutdown the PC by single push of the power button so that FC3 shuts down normally.
I have gone through the connect procedure numerous times but the mouse never works. I have the mouse and keyboard connected to the PS2 connectors directly (use a KVM also, but not at the moment). I do not want to use the USB connectors, even to get it going as I don't want to possibly be stuck using that.
USing Rescue I checked the xorg.conf file and everything seems fine in there when I compare to a different machine (different mouse & keboard through a KVM)
Any ideas on how to get things working?
Any reason to think that this is not a hardware issue? I have Logitech Wireless Duo myself (at least i think that's the brand) and it doen't give me any issues. From FC3 to FC4.
From: "Arthur Pemberton" dalive@flashmail.com
David Niemi wrote:
I have a Logitech wireless MX Duo that worked fine with FC3. I purchased this after I had installed and setup FC 3 and after playing around with the connects a few times it worked great.
Now I installed FC4 as a fresh install and everything worked during the Anaconda install, keyboard and mouse. When I reboot, nothing is recognised and I need to shutdown the PC by single push of the power button so that FC3 shuts down normally.
I have gone through the connect procedure numerous times but the mouse never works. I have the mouse and keyboard connected to the PS2 connectors directly (use a KVM also, but not at the moment). I do not want to use the USB connectors, even to get it going as I don't want to possibly be stuck using that.
Any ideas on how to get things working?
Any reason to think that this is not a hardware issue? I have Logitech Wireless Duo myself (at least i think that's the brand) and it doen't give me any issues. From FC3 to FC4.
The keyboard works during boot even through the KVM, but when I get into the first boot screen the mouse doesn't work and I can't tell if the keyboard is working either.
I am trying now a reinstall using a PS/2 keyboard and mouse as I had things during the first install in December.
On Sun, 2005-07-31 at 13:58 -0400, David Niemi wrote:
From: "Arthur Pemberton" dalive@flashmail.com
David Niemi wrote:
I have a Logitech wireless MX Duo that worked fine with FC3. I purchased this after I had installed and setup FC 3 and after playing around with the connects a few times it worked great.
Now I installed FC4 as a fresh install and everything worked during the Anaconda install, keyboard and mouse. When I reboot, nothing is recognised and I need to shutdown the PC by single push of the power button so that FC3 shuts down normally.
I have gone through the connect procedure numerous times but the mouse never works. I have the mouse and keyboard connected to the PS2 connectors directly (use a KVM also, but not at the moment). I do not want to use the USB connectors, even to get it going as I don't want to possibly be stuck using that.
Any ideas on how to get things working?
Any reason to think that this is not a hardware issue? I have Logitech Wireless Duo myself (at least i think that's the brand) and it doen't give me any issues. From FC3 to FC4.
The keyboard works during boot even through the KVM, but when I get into the first boot screen the mouse doesn't work and I can't tell if the keyboard is working either.
I am trying now a reinstall using a PS/2 keyboard and mouse as I had things during the first install in December.
Do you have encryption on?
On Mon, 2005-08-01 at 00:14 +0200, nodata wrote:
On Sun, 2005-07-31 at 13:58 -0400, David Niemi wrote:
From: "Arthur Pemberton" dalive@flashmail.com
David Niemi wrote:
I have a Logitech wireless MX Duo that worked fine with FC3. I purchased this after I had installed and setup FC 3 and
Do you have encryption on?
Nope, it appears to be a smp kernel issue.