manual insmod of usbcore, uhci and usb-storage works. Why not on boot?
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
manual insmod of usbcore, uhci and usb-storage works. Why not on boot?
I have updated the kernel from 2.6.7 to 2.6.22 to solve an issue. The issue is fixed but now my USB memory stick will not mount. I did an lsmod and found none of the USB drivers were there any more.
I manually installed the usbcore.ko, uhci-hcd.ko and usb-storage.ko modules and the mount worked. I edited the rc.sysinit to put these in the boot process since they weren't there. I don't know how the previous kernel was working without loading the modules but the mount always worked.
Now, every time I boot, usbcore and uhci-hcd are loaded at boot. But usb-storage refuses to load at boot. The mount then fails. Manually installing the module after boot does work.
All good questions. The target system is an embedded computer with limited space. The manufacturer used a "custom modified" version of linux originally based on slackware 9.1 with kernel 2.6.7. The person(s) who developed it then left that company so the support is non-existant.
My development system has 2.6.22.15 (PCLinuxOS) on it and has been very stable so I used the same version on this. I might upgrade it later but right now I'm trying to get the embedded system to work. I didn't need the additional hassle of trying to get my development system upgraded since gcc is on it. Part of the issue has been getting things to run on the embedded system when I can't build code on it due to limited space. Building on another system with the same kernel works OK.
The manufacturer provided a config file that their documentation says to use. I didn't want to modify it. The original kernel must have it built in since I don't see any modules installed. Don't know why it built as modules so I need to verify the config file for that. Newbie here.
I haven't used initrd before. I'll look into that as well as building USB in.
I found the problem. The scsi_mod and sd_mod modules were not being installed. Evidently, performing insmod on the USB modules pulled them in manually. Don't know how (or care at this point).
Adding these two modules prior to the USB modules in rc.sysint worked.
Maybe I'll be able to do this 'linux' thing after all. My confidence has been kind of low...
Hello LinuxTexan,
Good one...can you tell me how you get that usbcore.ko module?i too not having this same..but i dont know what to do....i copied the /drivers/usb/core file and i compiled but i am getting the below thing..but i didnt get .ko file....
sharief@sharief-desktop:~/Desktop/drivers/core$ make
make -C /lib/modules/2.6.26/build M=/home/sharief/Desktop/drivers/core modules
make[1]: Entering directory `/home/sharief/Desktop/kernelroot/linux2/linux-2.6.26'
Building modules, stage 2.
MODPOST 0 modules
make[1]: Leaving directory `/home/sharief/Desktop/kernelroot/linux2/linux-2.6.26'
sharief@sharief-desktop:~/Desktop/drivers/core$
I'm not sure on that one. You should find the .ko file under /lib/modules/'kernelrevnum'/kernel/drivers/usb/core where 'kernelrevnum is 2.6.... It is usually the only file there. If it's missing then your .config file probably doesn't have the usb options enabled when the kernel was built. Rebuilding the kernel with the proper options should recreate the file.
Actually i disabled the usb option when i build the kernel....tis is for college project...now i have to make the usb to work...so i copied the /drivers/usb/core file and i compiled...but i didnt get .ko file..thats what i am asking..i didnt get any source...searching from last month....can you help me
The source is in the kernel. Look in the directory where you placed the source when you built the kernel (most people use /usr/src or similar). The file should be there in a directory structure similar to the /lib/modules path. You will have to figure out the make commands for it.
It's probably simpler and less error prone to rebuild the kernel with USB active.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.