Sorry, hadn't seen the edit.

For the first instruction you posted, I get the following:
[root@localhost rvd]# modprobe usb-ehci
FATAL: Module usb-ehci not found.

The second command worked fine. I plugged the cam back in and here is the result:

[root@localhost rvd]# dmesg | tail -n 25
agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
i2c_adapter i2c-0: nForce2 SMBus adapter at 0x1c00
i2c_adapter i2c-1: nForce2 SMBus adapter at 0x2000
it87: Found IT8712F chip at 0x290, revision 6
bootsplash 3.1.6-2004/03/31: looking for picture...<6>...found (800x600, 9887 bytes, v3).
bootsplash: status on console 0 changed to on
bootsplash 3.1.6-2004/03/31: looking for picture...<6>...found (800x600, 9887 bytes, v3).
bootsplash: status on console 1 changed to on
bootsplash 3.1.6-2004/03/31: looking for picture...<6>...found (800x600, 9887 bytes, v3).
bootsplash: status on console 2 changed to on
bootsplash 3.1.6-2004/03/31: looking for picture...<6>...found (800x600, 9887 bytes, v3).
bootsplash: status on console 3 changed to on
bootsplash 3.1.6-2004/03/31: looking for picture...<6>...found (800x600, 9887 bytes, v3).
bootsplash: status on console 4 changed to on
bootsplash 3.1.6-2004/03/31: looking for picture...<6>...found (800x600, 9887 bytes, v3).
bootsplash: status on console 5 changed to on
eth0: no IPv6 routers present
usbcore: registered new driver usbfs
usbcore: registered new driver hub
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
[root@localhost rvd]#

Seems that usb may not have been started. I can do the following:

[root@localhost rvd]# /etc/init.d/usb restart
Initializing USB controller (ohci-hcd): [ OK ]
Initializing USB controller (ehci-hcd): [ OK ]
[root@localhost rvd]#

Afterwards I can do:

[root@localhost rvd]# lsusb
Bus 003 Device 004: ID 054c:0010 Sony Corp. DSC-S30/S70/S75/F505V/F505/FD92 Cybershot/Mavica Digital Camera
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
[root@localhost rvd]#

So, now the system recoginizes that I have USB, and that I have a cam. Seems I have to do this after each boot. Is there somewhere to put that restart command so I con't have to execute it manually after each reboot?

Now that the system knows that I have a digital cam, how do I go about mounting it? Nothing is in the /mnt directory except cdrom, cdrom2 and floppy. Also, why is it that when I click on the mnt directory it takes 30 seconds to get a response.

Nothing new appears after double clicking the devices icon. Getting closer, but still don't know how to access the cam.

It has taken me hours of Googling to get this far, but I may be making a bit of progress.

You would use chkconfig for that. I don't remember the exact syntax but something like this might work:
chkconfig --level 2345 usb on
That will start usb when you boot into runlevels 2,3,4or5.

The easiest way to access digital cameras is using gphoto2. Looks like your camera is supported:

I don't wish to butt in on the conversation but I too have the same problem. I'm trying to be mound a USB thumb drive on my machine. I am using slackware however. I recently recompiled downloaded the 2.6.16.1 and compiled it. I have everything working with the exception of usb.

In the compilation
I've built in USB device filesystem along with ehci support as well as all the USB Mass Storage support available


As root
*lsusb return nothing
*modprobe usb-ehci returns FATAL: Module usb_ehci not found
*modprobe usb-storage returns FATAL: Module usb_storage not found

dmesg | tail -n 25 doesn't show any new information or information that would be relevent to USB after any of these commands.

Are there any other other commands that might help shed light on the problem?

Ok, After trying a bunch of combinations Here's my lsmod
root@Visualize:~# lsmod
Module Size Used by
usb_storage 58288 -
md5 3720 -
ipv6 252480 -
uhci_hcd 32276 -
ehci_hcd 43568 -
3c59x 41584 -
snd_cd46xx 79332 -
snd_rawmidi 20384 -
snd_ac97_codec 94568 -
and_ac97_bus 1832 -
ohci_hcd 33740 -
root@Visualize:~#

lsusb still shows nothing though. I'm a little confused at this and plan on random tinkering to try to get to work but if anyone could tell me whats going on I'd appreciate it.

thanks

Do you have usbfs enabled in your kernel? Try this, edit /etc/fstab and add a line like this:
Then try to mount it:
mount usbfs
If it works then try lsusb again, and if it doesnt work then you need to rebuild your kernel with usbfs support.

I modified my '/ets/fstab' to include the line you printed above. I then rebooted the machine. mount usbfs did not return any errors but lsusb still did not return anything either.

I've looked through the usb support section of the kernel and I have the 'USB device filesystem' option check so it is built into the kernel.
I also have all the options under USB Host Controler Drivers checked as modules
USB Mas Storage support is checked as a modules and all the options under it are checked as built in

I'm going to try building everything into the kernel to see if there is any change. Is there something else that I might be missing in the kernel compilation? I looked under filesystems but didn't see anything that could be related to USB. Is there something else I could be forgetting?

Does the USB port work? Do you have another OS you can boot with to check that the port actually works, and also that the thumb drive is working.

If not then maybe this will help isolate if the hub works or maybe the thumb drive is bad.
Try a fresh boot without the thumb drive plugged in then do this:
ls -l /proc/bus/usb/
If you have any directories like 001 002 then your usb hub is working. If there is a file /proc/bus/usb/devices then do this
cat /proc/bus/usb/devices

Then plug in the thumb drive and do another
cat /proc/bus/usb/devices
And look for the thumb drive.

<edit> Do you have MMC/SD Card support enabled in your kernel?

Well I KNOW the hardware works because I transfered the 2.6 kernel to the computer using the usb thumb drive. It's an Issue I've been tyring to figure out for a bit now. I recently did an entire reinstall of Slackware to try to get it to work. The thing that is REALLY throwing my is that if I boot with the old kernel now I get the exact same thing. I figure it has to be something really abstract involving the hardware. It doesn't seem to make sense that I would boot with a new kernel and the old kernel would stop working.

2.4 doesn't have the directory /proc/bus/usb
2.6 Has /proc/bus/usb but there is nothing in there.

I appreciate you thoughts on the matter

Under "USB Mass Storage support" I have "Microtech/ZiO! CompactFlash/SmartMedia support" selected. Is this what you mean?

I was able to find this under lspci

...
00:0f.2 USB Controller: Broadcom OSB4/CSB5 OHCI USB Controller (rev 04)
...

Does this mean anything to anyone? Has anyone worked with this controller before?

thanks

I'm really just guessing now but "MMC/SD Card support" is an option by itself in the drivers section.

I just noticed you dont have the module usbcore loaded. Try modprobe usbcore, look at dmesg and /var/log/messages for anything interesting.

Your other modules seem to be loaded:
usb_storage 58288 -
uhci_hcd 32276 -
ehci_hcd 43568 -
ohci_hcd 33740 -

I don't know if the uhci_hcd will cause problems since you seem to have a ohci controller. You only need one of those modules but I don't think it will hurt to have the other loaded.

I tried 'modprobe usbcore' but got

when I typed dmesg|tail -n 25 I got this

drivers/usb/core/inode.c: usbfs: mount parameter error:
ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controler (OHCI) Driver (PCI)
ohci_hcd: block sizes: ed 64 td 64
ohcu_hcd 0000:00:0f.2: OHCI Host Controler
drivers/usb/core/inode.c: creating file 'devices'
drivers/usb/core/inode.c: creating file '001'
ohci_hcd 0000:00:0f.2: new USB bus registered, assigned bus nimber 1
ohci_hcd 0000:00:0f.2: request interrupt 33 failed
ohci_hcd 0000:00:0f.2: USB bus 1 deregistered
ohci_hcd 0000:00:0f.2: init 0000:00:0f.2 fail, -38
ohci_hcd: probe of 0000:00:0f.2 failed with error -38
...
ehci_hcd: block sizes: qh 128 qtd 96 itd 192 sitd 96
USB Universal Host Controller Interface driver v2.3
...

It looks like usbcore is trying to start but is failing with the error 38.

usb_storage does not register initially but using modprob usb_storage executes fine and the follwoing lines are added o the dmesg
...
usbcore: registered new driver usb-storage
USB Mass Storage support registered

I guess the next step is to search for what error 38 is. I'll post it if/when I find it.


Thanks

I found this thread:
Here

It seams to address the problems I'm working through but I don't understand how to pass the option pci=routeirq. Does anyone know exactly what they are talking about?

I was able to pass the argument pci=routeirq using the following line in my lilo.comf file
After doing this I am still getting the interrupt request failure in my dmesg output. Anyone have any other ideas?

thanks