ok im a little bit of a newbie with linux, i know my way around etc etc, thing is i grabed a copy of Fedora Core 4 RC2 the othet day and my wireless keyboard wont work after its booted up. Im able to move through the grub menu and winodws just not able to do anything with it once inside.
I did a dmesg and it shows as their aswell as my mouse (they use the same thing) any ideas anyone?

AFAIK: the fact that the keyboard and mouse are wireless shouldn't matter! The computer just sees a mouse and keyboard.

Have you checked the modules to see if the keyboard and mouse drivers are there?

So, I'd try the obvious: bum a wired keyboard and mouse and reboot - kudzu should detect the change in hardware. If this works you can swap back, and keep the configuration.

But you can boot fine? The keyboard and mouse worked all through the installation?

yeah the keyboard started working after i set the partitions, but i had to have a wired one in there so i could do the meida check, funny thing is it worked before that (wireless kb). I tried that, added wired kb + mouse booted, kudzu didnt do detect changes i think becase i needed them for set up, i did dmesg again, didnt see the USB kb/mouse, booted with just usb kb/mouse and didnt detect any changes and still cant use the kb


*some how my keyboard just started working not a clue why tho*

*and yet again its not working...*

Well - does the install work OK if you have a wired kbd+mouse?
Also - do lsmod and post the output.

If I remember right, the usb keyboard and mouse have their own modules.

(Aside: Oh - and humour an old man and capitalise your personal pronoun "I" please - you'll feel more important that way It's no big really, but you'll see the difference.)

I just got a new HDD, i reinstalled FC4 on it, first i need to use a wired keyboard to get past the media test, then it doesnt detect i have any mouse detected so i select generic usb, i go through and set everything up, once it got to the root password selector I tried using my wireless keyboard, and it work, after that it kept working for the remainder of the set up.

Module Size Used by
nls_utf8 2113 1
ntfs 183696 1
usb_storage 72073 1
parport_pc 28933 1
lp 13001 0
parport 40585 2 parport_pc,lp
autofs4 27205 0
sunrpc 167813 1
ipt_REJECT 5569 1
ipt_state 1857 3
ip_conntrack 41369 1 ipt_state
iptable_filter 2881 1
ip_tables 19649 3 ipt_REJECT,ipt_state,iptable_filter
dm_mod 58229 0
video 15941 0
button 6609 0
battery 9412 0
ac 4805 0
md5 4161 1
ipv6 269505 8
joydev 9601 0
uhci_hcd 33241 0
ehci_hcd 40525 0
emu10k1_gp 3649 0
i2c_viapro 7889 0
i2c_core 22081 1 i2c_viapro
snd_emu10k1 124741 0
snd_util_mem 4673 1 snd_emu10k1
snd_hwdep 9057 1 snd_emu10k1
snd_via82xx 30081 3
gameport 18633 3 emu10k1_gp,snd_via82xx
snd_ac97_codec 75960 2 snd_emu10k1,snd_via82xx
snd_pcm_oss 51185 1
snd_mixer_oss 17728 3 snd_pcm_oss
snd_pcm 100041 4 snd_emu10k1,snd_via82xx,snd_ac97_codec,snd_pcm_oss
snd_timer 33477 2 snd_emu10k1,snd_pcm
snd_page_alloc 9669 3 snd_emu10k1,snd_via82xx,snd_pcm
snd_mpu401_uart 10049 1 snd_via82xx
snd_rawmidi 29793 2 snd_emu10k1,snd_mpu401_uart
snd_seq_device 8781 2 snd_emu10k1,snd_rawmidi
snd 57157 11 snd_emu10k1,snd_hwdep,snd_via82xx,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_mpu 401_uart,snd_rawmidi,snd_seq_device
soundcore 10913 4 snd
sk98lin 175777 0
tulip 55265 0
floppy 65141 0
ext3 132553 1
jbd 86105 1 ext3
sata_via 8389 2
libata 47045 1 sata_via
sd_mod 20673 5
scsi_mod 147593 3 usb_storage,libata,sd_mod




and dmesg | grep usb
usbcore: registered new driver usbfs
usbcore: registered new driver hub
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.01:USB HID core driver
usb 1-6: new high speed USB device using ehci_hcd and address 4
usb 2-2: new full speed USB device using uhci_hcd and address 2
usb 3-1: new low speed USB device using uhci_hcd and address 2
input: USB HID v1.00 Keyboard [Mlk Cordless USB Mouse & Keyboard] on usb-0000:00:10.1-1
usbcore: registered new driver usb-storage
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete

The wired mouse and kebd you used: were these usb too?

Anyway - assuming they were - while I don't see things like mousedev and usb-mouse in your lsmod list, you have all the usb modules and the usbhid (human interface device) module loaded so that should be fine. (Someone correct me if I'm wrong!)

the dmesg indicates a mass media device - which stands out to me because I have had conflicts between usb mass media and other usb drivers myself in the past (in my case, the ipaq module conflicted with usb_storage for my PPC - the PPC kept getting listed as a mass storage device (which is half right) and prevented sync via usb-ppp.) So... do you have a mass media device plugged in as well? Or do you have a usb port on the mouse or the keyboard which is not present in the wired usb mouse or keyboard that you used in the installation.

What you are seeing is that one usb keyboard/mouse will work and another will not. You need to find out what the differences are between them. If the kernel thinks your mouse (for eg) is actually a mass media device, then you won't be able to use the mouse as a mouse.

Another thing to try is to take a look in X86config to check that the mouse is listed as an input device.
a-la http://lists.debian.org/debian-lapto.../msg00274.html which is a similar problem for debian. Read the follow ups as well.