Enable USB?

jmkelm08 · 06-24-2006, 01:32 AM

I think I'm getting really close to solving my kernel compiling trouble, but I need some help. After applying the patch correctly to the kernel, the "make uImage" command required a cross-compiler to work. A guy I know knew how to make one, so he did that for me, and after some debugging and adding and removing of kernel options, we were able to successfully run "make clean dep uImage" on a seperate linux box. After that, we successfully executed "make modules" then "make modules_install". During the "make modules_install" phase, we recieved and error message about not being able to find "/sbin/depmod.old". I decided to try copying depmod to depmod.old and ran the command again without any errors. We then went to try to copy the kernel image to the MIP405 to boot it, but the images folder there were 3 files. One was a Makefile, one was vmlinux.gz, and the other was a link to vmlinux.Uboot. We figure the Uboot one is what we really need, but the link says that what it is pointing to does not exist(the link is for a file in the same folder as the link). We tried using the vmlinux.gz and using the "dd" command to put it on /dev/hda2 and booting from it, but it did not succeed.
I have two main questions:
1) Could the broken link/missing file be because of the depmod.old trick that I pulled?
2) Can you run all of the make commands like we did and copy the image at the end to the MIP405 if you use a cross-compiler? Will this take care of the modules to? If not, can you give me a walk through of how I should go about this?

Bruce Hill · 06-25-2006, 05:36 AM

I'm sorry, but you're over my head now. If someone doesn't show up here who can help you, I'd try to compile the kernel on the MIP405, and try the IRC channel and mailing list at http://penguinppc.org/embedded/#community

jmkelm08 · 06-30-2006, 04:07 AM

It appears that the kernel was not the problem. After hours of messing with compiling a new kernel, I finally got one working, but I recieved the same pipesize error from earlier. A friend of mine messed around with installing modules and stumbled across a configuration that allowed me to mount a USB device, but he could not figure out what made it work, so we copied all the commands he had run from the .bash_history file and put them in a script and ran it. After a reboot, this script was able to get USB running again. I took out several of the lines that were not needed in the script, such as 'ls' and 'vi' commands, but I don't know what of the remaining lines I can remove. If someone knows the order the commands should be run, I would appreciate the help.

Here is the current script:

Code:

insmod usbcore
insmod usb-uhci
mount
mount -t usbdevfs none /proc/bus/usb
cd /proc/bus/usb
rmmod usb-uhci
rmmod usbcore
insmod usb-uhci
insmod fat
insmod vfat
insmod sd_mod
mount -t usbdevfs none /proc/bus/usb
insmod usb-storage
mount /dev/sda1 /mnt/usb
cd /mnt/usb
ls

I still get a pipesize error when I plug usb devices in after usb starts, but I can still use the devices.

jmkelm08 · 07-14-2006, 12:05 PM

To finish up for anyone who is searching for an answer to this problem in the future, unfortunately I was unable to find a way to solve the pipesize error in the 2.4 kernel on the MIP405. In the end, I upgraded to 2.6.12 kernel and USB worked perfectly. I would still like to know why 2.4 would not work, but atleast a solution was found.

Bruce Hill · 07-14-2006, 06:45 PM

I'm glad you got it working, and believe my advice in post #11 was to compile 2.6.

As for the error, I've no clue. But you could always email someone at either the Linux Kernel Mailing List (LKML) or that PeguinPPC.org mailing list. They would be better qualified to help you.

Also I'd like to say I admire your tenacity.