Hi,

I just installed RedHat 7.2 last week and this is my frist try at Linus. I got so sick of my Winkows ME crashing all the time. I said I would never buy another Windows Disc. again.

Any way my question is when I boot from my system disk it says my USB Failed but when I boot from the Floppy I saved during the install it works Fine. Is the Floppy kernel and my HD kernel dif.? If so how do I fix it? I am dumb about Linux.

Willie

check your /etc/modules.conf file....

you may have the wrong usb module loading up.... they are usually usb-uhci or just uhci... try changing them around and see what happens...

If you are using a Via chipset on your motherboard then usually the USB-UHCI module should work but if you are using anything Intel based then just the UHCI module will do the trick.

If you still cant get it to work just recompile your kernel with USB filesystem support and you should be good to go.

Cheers

thats what i said therion, dude

Just trying to shed some light on what both of them do. And you didn't mention USB Filesystem either.

Hi again,

I have a USB external CD-RW drive. As I said before when I boot from my floppy the USB works fine and mounts a CD drive. When I boot from my hdd it Fails. Below is a section from my boot.log booting from my hdd:

Feb 13 08:27:24 linuxbox rc.sysinit: Mounting USB filesystem: succeeded
Feb 13 08:27:24 linuxbox modprobe: /lib/modules/2.4.7-10/kernel/drivers/usb/usb-ohci.o:
Feb 13 08:28:00 linuxbox keytable: Loading keymap: succeeded
Feb 13 08:27:24 linuxbox modprobe: init_module: No such device
Feb 13 08:27:24 linuxbox modprobe: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
Feb 13 08:27:24 linuxbox modprobe: /lib/modules/2.4.7-10/kernel/drivers/usb/usb-ohci.o: insmod /lib/modules/2.4.7-10/kernel/drivers/usb/usb-ohci.o failed
Feb 13 08:27:24 linuxbox modprobe: /lib/modules/2.4.7-10/kernel/drivers/usb/usb-ohci.o: insmod usb-ohci failed
Feb 13 08:27:24 linuxbox rc.sysinit: Initializing USB controller (usb-ohci): failed

What I really don't understand the kernel files on my hdd and the one on the floppy are the exactly the same. Just to make sure I copied the one on the floppy to the hdd and got the same ansewer. I should note I am useing Red Hat 7.2. Sence I am new to linux and a lot I don't understand. I also copied the intrd.img file to hdd. It didn't make any difference.

:smash:

------------------------------------------

Mother Board- PC Ware M741LMRT
Processor - Celron 366
RAM - 512
HDD - Maxor 40 Gig

Check to make sure that the modules it is looking for exist on your partition.

It is module is there at /lib/modules/2.4.7-10/kernel/drivers/usb/usb-ohci.o

I know the module works because it I move it from this location the floppy boot fails. When I put it back the floopy boot works ok but the hdd boot still fails.

I am at a loss as to why!!!

Ok, i know there must be a fix but if i was you and nobody can help you get the module working, try to compile a new kernel like 2.4.17 and build new modules for it so incase the module(s) is bad it will replace it with the new ones.

Here's a cheap way to go about... which doesn't involve a kernel compile either.

Copy the kernel on the floppy onto the hard drive. Give it a different name then vmlinuz, edit grub or lilo.conf (I could help you with lilo) so you have both the original HD kernel on the Hard drive and the floppy kernel on the hard drive as choices. Then see if it works from the Hard drive.

Cheers,

Finegan

this may seem to be the mother of dumb questions but: finegan yu were saying to copy the kernel onto a floppy... how is that when the linux-version-tar.gz seems to be over 25mb in size... would you unpack it and take a certain file out (that is actually the kernel) or not...how does that work?

I had already said I had copied the kernel on the floppy to my hdd. It didn't make any difference. I have never tryed to compile the kernnel but you have learn sometimes. I have downloaded 2.4.17. I will let you know results. Thanks for all the help and suggestions.

No problem, come back if 2.4.17 does't work out, it should though i mean i got it to work after a few compiles.

Yeah, I just can't read... Good luck with 2.4.17. It'll probably take a couple tries of accidently leaving this and that out. Just remember that compile times used to be in hours...

Cheers,

Finegan