USB device won't mount

After mush gnashing of teeth, I was able to mount the camera manually.
I still have a small problem though, a device is plugged into the USB freezes and I have to restart with the device unplugged to get my internet connect back.

Thanks for your support request. However, I believe this going to end up being a bug. You could either submit a bug against linux-source-2.6.15 or answer some more questions here. Either way we will want the output of 'lsusb' and the complete output of 'dmesg' to be better able to help you out.

Hi thanks for the reply

I finally mounted my dSLR (Nikon d70s) via USB 2.0 device. The camera is running a 1G SanDisk Extreme III CompactFlash card formatted in camera to FAT32. If I restart the computer fresh and plug in the USB I am able to mount the device manually. However, it will not mount if there has been network activity. That is to say, if I have opened my web browser at all before plugging in the USB no /dev/sd* will appear no matter how many times I try. Likewise after I have mounted the camera and cp the pictures to ~/ the internet hangs and I have to restart my computer all over again to get an internet connect back... grrrr...

I just installed Dapper this weekend. this is my first Linux OS and I am very happy besides this one problem. Any help you can provide would be great!

I am adding the following information to help with diagnosing the problem. Please keep in mind that I am very much a 'user' not a 'doer' when it comes to Linux.

1. First I tried to find my USB ports with nothing plugged in
bolsen@bolsen-desktop:~$ lsusb
Bus 004 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000

2. Then ran dmesg with no devides plugged in
bolsen@bolsen-desktop:~$ dmesg > dmesg1

3. Next I plugged in the camera without the card and ran dmesg again
bolsen@bolsen-desktop:~$ dmesg > dmesg2

3. Then with the card inserted and the camera on and reading "PC connected" on the LCD I ran dmesg a third time
bolsen@bolsen-desktop:~$ dmesg > dmesg3

4. Then I compared the two files dmesg1 and dmesg2
diff dmesg1 dmesg2 > diff1_2

5. Then I compared the two files dmesg1 and dmesg3
diff dmesg1 dmesg3 > diff1_3

6. The resulting file of diff1_2 was empty (no difference)

7. The results of diff1_3 are here:
287a288,321
> [17180048.272000] usb 1-2: new full speed USB device using uhci_hcd and address 2
> [17180048.980000] Initializing USB Mass Storage driver...
> [17180048.984000] scsi0 : SCSI emulation for USB Mass Storage devices
> [17180048.988000] usb-storage: device found at 2
> [17180048.988000] usb-storage: waiting for device to settle before scanning
> [17180048.988000] usbcore: registered new driver usb-storage
> [17180048.988000] USB Mass Storage support registered.
> [17180049.032000] irq 5: nobody cared (try booting with the "irqpoll" option)
> [17180049.032000] [<c013ee82>] __report_bad_irq+0x22/0x80
> [17180049.032000] [<c013ef78>] note_interrupt+0x68/0xc0
> [17180049.032000] [<c013e83c>] __do_IRQ+0xbc/0xe0
> [17180049.032000] [<c010596a>] do_IRQ+0x1a/0x30
> [17180049.032000] [<c01040aa>] common_interrupt+0x1a/0x20
> [17180049.032000] [<c0172410>] sys_dup2+0x0/0x140
> [17180049.032000] [<c0102feb>] sysenter_past_esp+0x54/0x79
> [17180049.032000] handlers:
> [17180049.032000] [<f88d0730>] (usb_hcd_irq+0x0/0x60 [usbcore])
> [17180049.032000] [<f8a206f0>] (rhine_interrupt+0x0/0x240 [via_rhine])
> [17180049.032000] Disabling IRQ #5
> [17180054.836000] Vendor: NIKON Model: D70s Rev: 1.00
> [17180054.836000] Type: Direct-Access ANSI SCSI revision: 02
> [17180054.868000] usb-storage: device scan complete
> [17180054.948000] Driver 'sd' needs updating - please use bus_type methods
> [17180056.096000] SCSI device sda: 2001889 512-byte hdwr sectors (1025 MB)
> [17180056.852000] sda: Write Protect is off
> [17180056.852000] sda: Mode Sense: 0f 00 00 00
> [17180056.852000] sda: assuming drive cache: write through
> [17180059.120000] SCSI device sda: 2001889 512-byte hdwr sectors (1025 MB)
> [17180059.876000] sda: Write Protect is off
> [17180059.876000] sda: Mode Sense: 0f 00 00 00
> [17180059.876000] sda: assuming drive cache: write through
> [17180059.876000] sda: sda1
> [17180061.136000] sd 0:0:0:0: Attached scsi removable disk sda
> [17180061.164000] sd 0:0:0:0: Attached scsi generic sg0 type 0

8. With the device now plugged in I can see it
Bus 004 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 002: ID 04b0:040d Nikon Corp.
Bus 001 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000

9. And I can mount it
sudo mount -t vfat /dev/sda1 /media/usbCF

10. I can read it
bolsen@bolsen-desktop:/media/usbCF/dcim/100nd70s$ ls
dsc_0101.jpg dsc_0145.jpg dsc_0195.jpg dsc_0245.jpg dsc_0296.jpg
dsc_0102.jpg dsc_0146.jpg dsc_0196.jpg dsc_0246.jpg dsc_0297.jpg
dsc_0103.jpg dsc_0147.jpg dsc_0197.jpg dsc_0247.jpg dsc_0298.jpg
dsc_0104.jpg dsc_0148.jpg dsc_0198.jpg dsc_0248.jpg dsc_0299.jpg
dsc_0105.jpg dsc_0149.jpg dsc_0199.jpg dsc_0253.jpg

11. BUT. Now the internet does not work!!! Also I noticed if I try and mount the camera after there has been activity on the network it will not mount. Actually no /dev/sda will appear at all if the network has been accessed. I can't see to figure out why there is a conflict between my USB and ethernet!

I hope this extra info is helpful. At least I have learned something about Linux in the process.

Ben

Have you tried this in the latest release 6.10? Does it do the same thing?

No, I was hoping I could use 6.06 as everything else works fine

That's understandable, I just figured because the newer versions have more hardware support, boots faster, etc etc that you may want to try it out, even as a live cd to see if the problem persists.

Best Regards,

Williamts99

Yesterday I got the bad idea to update from dapper to edgy. The process failed and I decide to return to Dapper. Now the system seems to be completelly lost in the electronic jungle.
I lost my X and after one hour of work I half recovered the startx which now produce an ugly screen. Today I discover that the usb pen is not longer recognized. There is no usb point in /media.
I afraid to produce more damage to my programs.
It is supossed that I need include a line (devfs=mount) in lilo.conf (according to /usr/share/doc/devfsd/README.Debian) but I do not have lilo.
Please, any idea? Any alternative way to recover the automount capabilities?
With best regards,
Gustavo

I forgot to send the lsusb info:
gcordoba@xterm2:~$ lsusb
Bus 006 Device 002: ID 058f:6387 Alcor Micro Corp.
Bus 006 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
Bus 002 Device 003: ID 045e:0083 Microsoft Corp. Basic Optical Mouse
Bus 002 Device 001: ID 0000:0000
gcordoba@xterm2:~$

Sorry, maybe this can be usefull too:
gcordoba@xterm2:~$ mount
/dev/sda1 on / type ext2 (rw,errors=remount-ro)
proc on /proc type proc (rw)
/sys on /sys type sysfs (rw)
varrun on /var/run type tmpfs (rw)
varlock on /var/lock type tmpfs (rw)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
devshm on /dev/shm type tmpfs (rw)
lrm on /lib/modules/2.6.17-11-386/volatile type tmpfs (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
gcordoba@xterm2:~$

gcordoba,

Would you please consider opening your own support request as it gets very confusing having more then one problem per support request. You can easily follow the link below and start your own personal support request.
https://answers.launchpad.net/ubuntu/+addticket

Best Regards,

Williamts99

Thanks,
I fixed it by updating again to edgy via update-manager.
Bye,
Gustavo