modprobe.old

[imehl]

when i boot the kernel i get a warning:
WARNING: modprobe.old: I am not the old version

i think i overwrote the modprobe.old file. is there a way to restore this file??

[bwkaz]

Let me guess. You installed module-init-tools, right? More than once, right? You are only supposed to run make moveold ONCE. If you run it twice, you'll overwrite your old modutils programs.

There is no easy way to restore the files, no (because they were not necessarily deleted -- they could have just been overwritten, in which case only a low-level analog scanning-tunneling-microscope type recovery will be able to undo the disk writes). Even if they were deleted, if you're using ext3, you need to know that it does not support undeletes the same way ext2 does -- with ext3, the block pointers are zeroed when a file is deleted. Every ext2 undelete program that I've ever looked into requires those block pointers to be intact (because they all use those pointers to find out where on the disk the files actually are). Some other journalled filesystems also work the same way.

There are no problems with your current setup, if you only plan on using 2.6 kernels. But you cannot load modules into a 2.4 kernel anymore, if you're missing the old version of modprobe (or insmod).

You might be able to reinstall modutils, then reinstall module-init-tools (and run make moveold that time, but NEVER AGAIN). That will only work if modutils doesn't check the kernel version, though (I don't expect that it does, but you never know)...

[imehl]

yes, i wouldn't have any problem running 2.6 kernels except my keyboard doesn't work when i boot the 2.6.7 kernel. sorry to be so vague but i have no idea how to begin to address this problem. i think it has something to do with the fact that my keyboard is USB. i definitely built the kernel with USB support but how do i check that USB is working??

[imehl]

the only relevant lines in /var/log/messages on usb are:

usbcore: registered new driver usbfs
usbcore: registered new driver hub
ehci_hcd 0000:00:1d.7: irq11, pci mem fd80fc00
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned 2004-May-10
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 8 ports detected
hub 1-0:1.0: usbcore: registered new drive usbhid
drivers/usb/input/hid-core.c: v2.0: USB HID core driver

any advice

[bwkaz]

You've loaded HID support, which should cover any input device (keyboards, mice, etc.). If the keyboard still isn't working... hmm.

Does the keyboard work in any other kernel that you've kept around? Try booting to one of those kernels maybe?

If you haven't kept a working kernel around, then start doing so now. :p

[imehl]

my keyboard still works in an old 2.4.20 kernel. i can't load to x though because i get the error:
gpm[1237] /dev/mouse: no such device

[imehl]

found this in an old post:

in the boot config file add, "pci=noapci". In lilo it would be on the:
append="pci=noapci"

how would you do this in grub?? is this worth doing??

[bwkaz]

Originally posted by imehl
i get the error:
gpm[1237] /dev/mouse: no such device This means that you have a /dev/mouse file, and it points at a real device node somewhere (probably, anyway -- /dev/mouse is *almost* invariably a symlink to the real device, either /dev/psaux for PS/2 mice or /dev/input/mice for USB mice). However, there is no driver loaded for that device node.

If it points at /dev/input/mice, then try to /sbin/modprobe hid and/or mousedev. If it points at psaux, then try to /sbin/modprobe the PS/2 mouse driver (I think it's psmouse, but I'm not sure -- it is possible that it can't even be a module in kernel 2.4, but I don't think that's the case).

The pci=noacpi option would only help if you have the hid/mousedev modules loaded but still don't have a mouse (or you have the PS/2 mouse module loaded but it still doesn't work). Or if you can't load the appropriate module for your mouse. If you want to try it, find the relevant grub section in /boot/grub/menu.lst (or grub.conf for old versions of grub), and edit the kernel line to add pci=noacpi at the end. Keep it inside the quotes though.

[imehl]

when booting i get the message:
FATAL: module hid not found

does this mean i didn't build this module into the kernel?
what line do you check for this in the kernel config file?
in what log file can i find this error message or more information? i checked dmesg and boot.log and it is not there.

[bwkaz]

That's not logged by default anywhere (unless your distro has patched its modprobe command).

What it means is that you either built HID support directly into the kernel, or you left it out completely. To get rid of the message, either find the config file that's trying to load the "hid" module and comment that line out, or reconfigure your kernel and build HID support as a module.

The two options you need for the latter are CONFIG_USB_HID (set to "M") and CONFIG_USB_HIDINPUT (set to "Y") in "make config". Otherwise set Device Drivers --> USB support --> USB Human Interface Device (full HID) support (and also "HID input layer support" in the same place) in menuconfig / xconfig / gconfig.

If you set CONFIG_USB_HID to Y, then try to find the config file that controls modules in your kernel, and try to disable the "hid" module from being loaded. If it's built in, there's no reason to try to load the module.

[jimihieu]

That's not logged by default anywhere (unless your distro has patched its modprobe command).

What it means is that you either built HID support directly into the kernel, or you left it out completely. To get rid of the message, either find the config file that's trying to load the "hid" module and comment that line out, or reconfigure your kernel and build HID support as a module.

The two options you need for the latter are CONFIG_USB_HID (set to "M") and CONFIG_USB_HIDINPUT (set to "Y") in "make config". Otherwise set Device Drivers --> USB support --> USB Human Interface Device (full HID) support (and also "HID input layer support" in the same place) in menuconfig / xconfig / gconfig.

If you set CONFIG_USB_HID to Y, then try to find the config file that controls modules in your kernel, and try to disable the "hid" module from being loaded. If it's built in, there's no reason to try to load the module.

hi
i got same problems...i tried to recompile the kernel and make those options stated above as M.
however my usb mouse still wont work and it keep being detect as /dev/psaux not /dev/input/mice at boot up
how can i fix this please?
sorry im a newbie to linux.
Oh im using X11R6 in DSL distro.
thanx

[bwkaz]

Well, quite a bit has changed regarding the Linux kernel's input layer in the two years that it's been since I posted that, actually. ;)

For one, any moderately-recent 2.6 kernels (actually almost all of them now) don't use /dev/psaux for PS/2 mouse input. They use /dev/input/mice, just like for USB mice. The reason is that the PS/2 driver is now sitting "under" the generic input layer (which was abstracted out of the USB input driver during the development of 2.6 IIRC), so exposing the mouse movements via /dev/input/mice makes more sense (given the architecture) than a separate device file.

So /dev/psaux is really not required; anything that you see there will also show up on /dev/input/mice. You should be able to configure your X server to use either file; they should be equivalent.

Maybe you should back up a bit: Exactly what isn't working? Start a different thread when you do that, too, because I'm not so sure it's anything related to this one. :)