2006/2/23, Kari Myllykangas <kari.myllykangas@xxxxxxxxx>:
Tree clues:
1. When I boot the fedora, the ligt is linking like it shoud. It means that the fedora founds the usb mouse
2. When I wrote the ansewer to the fedora list, the usb mouse started to work suddenly. It started to work after about ten minutes. I was so exited that I didn't check /var/log/messages. Then I rebooted but the mouse didn't work any more after reboot. Afterwards I tried to found from /var /log/messages what has happened. I think that this hapened when usb mouse started to work:
Tree clues:
1. When I boot the fedora, the ligt is linking like it shoud. It means that the fedora founds the usb mouse
2. When I wrote the ansewer to the fedora list, the usb mouse started to work suddenly. It started to work after about ten minutes. I was so exited that I didn't check /var/log/messages. Then I rebooted but the mouse didn't work any more after reboot. Afterwards I tried to found from /var /log/messages what has happened. I think that this hapened when usb mouse started to work:
Feb 23 23:18:33 localhost gconfd (kari-2975): Kirjoitettavan asetuslähteen osoite "xml:readwrite:/home/kari/.gconf" kohdassa 0 selvisi
...and that in english: The address of writable setupfile in the row 0 was found "xml:readwrite:/home/kari/.gconf"
3. Now I logged out (not rebooted) and then the mouse started to work. In the /var/log/messages was the following:
I was logged as root and the mouse didn't work
2006/2/23, James Wilkinson <fedora@xxxxxxxxxxxxxxxxxxx>:Kari Myllykangas wrote:
> I have problem with my optical usb mouse on fedora core 4. It worked fine
> in
> the kernel of 2.6.14-1.1656 and before that but not any more on
> 2.6.15-1.1830 or 1831. The cursor stays on the screen but it doesn't
> move. If I use the usual "non usb" mouse, that one works.
>
> I have tried all tips which I found from the internet. I can't solve
> this problem by myself alone
You know USB devices are hot-pluggable (which means you can plug them in
while the system is running)? Try unplugging it and re-plugging it.
Try it in a different USB port.
Open a terminal and run
su - -c "tail -f /var/log/messages"
You will be prompted for the root password.
You will see the "end" of the /var/log/messages file: many system
messages are logged here. Plug in the mouse, and see what lines are
output.
Hope this helps,
James.
Tree clues:
1. When I boot the fedora, the ligt is linking like it shoud. It means that the fedora founds the usb mouse
2. When I wrote the ansewer to the fedora list, the usb mouse started to work suddenly. It started to work after about ten minutes. I was so exited that I didn't check /var/log/messages. Then I rebooted but the mouse didn't work any more after reboot. Afterwards I tried to found from /var /log/messages what has happened. I think that this hapened when usb mouse started to work:
Tree clues:
1. When I boot the fedora, the ligt is linking like it shoud. It means that the fedora founds the usb mouse
2. When I wrote the ansewer to the fedora list, the usb mouse started to work suddenly. It started to work after about ten minutes. I was so exited that I didn't check /var/log/messages. Then I rebooted but the mouse didn't work any more after reboot. Afterwards I tried to found from /var /log/messages what has happened. I think that this hapened when usb mouse started to work:
Feb 23 23:18:33 localhost gconfd (kari-2975): Kirjoitettavan asetuslähteen osoite "xml:readwrite:/home/kari/.gconf" kohdassa 0 selvisi
...and that in english: The address of writable setupfile in the row 0 was found "xml:readwrite:/home/kari/.gconf"
I was logged as root and the mouse didn't work
Feb 23 23:23:17 localhost gdm(pam_unix)[2832]: session closed for user root
Feb 23 23:23:17 localhost dbus: avc: 1 AV entries and 1/512 buckets used, longest chain length 1
Feb 23 23:23:17 localhost kernel: agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0.
Feb 23 23:23:17 localhost kernel: agpgart: Putting AGP V3 device at 0000:00:00.0 into 4x mode
Feb 23 23:23:17 localhost kernel: agpgart: Putting AGP V3 device at 0000:01:00.0 into 4x mode
Feb 23 23:23:17 localhost kernel: [drm] Loading R200 Microcode
Now the mouse works
Feb 23 23:23:35 localhost gdm(pam_unix)[2832]: session opened for user kari by (uid=0)
So What????
yours
Kari Myllykangas
Feb 23 23:23:17 localhost dbus: avc: 1 AV entries and 1/512 buckets used, longest chain length 1
Feb 23 23:23:17 localhost kernel: agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0.
Feb 23 23:23:17 localhost kernel: agpgart: Putting AGP V3 device at 0000:00:00.0 into 4x mode
Feb 23 23:23:17 localhost kernel: agpgart: Putting AGP V3 device at 0000:01:00.0 into 4x mode
Feb 23 23:23:17 localhost kernel: [drm] Loading R200 Microcode
Now the mouse works
Feb 23 23:23:35 localhost gdm(pam_unix)[2832]: session opened for user kari by (uid=0)
So What????
yours
Kari Myllykangas