Re: Problems Mounting Digital Camera

From: Tony Godshall (togo_at_of.net)
Date: 06/02/05

  • Next message: Winston Smith: "Re: excluding files w/ tar" 
    Date: Thu, 2 Jun 2005 08:04:49 -0700
To: Romulo Sousa <romulosousa@gmail.com>

    According to Romulo Sousa,
    > On 6/2/05, Adam Mercer <ramercer@gmail.com> wrote:
    > > On 02/06/05, Romulo Sousa <romulosousa@gmail.com> wrote:
    > >
    > > > any clues?
    > >
    > > what shows up in your syslog, I get the following when I plug my camera in
    >
    > Jun 2 11:26:19 localhost kernel: usb-uhci.c: $Revision: 1.275 $ time
    > 12:08:47 Mar 25 2005
    > Jun 2 11:26:19 localhost kernel: usb-uhci.c: High bandwidth mode enabled
    > Jun 2 11:26:19 localhostkernel: usb-uhci.c: v1.275:USB Universal Host
    > Controller Interface driver
    > Jun 2 11:26:19 localhost kernel: usb.c: registered new driver usbkbd
    > Jun 2 11:26:19 localhost kernel: usbkbd.c: :USB HID Boot Protocol
    > keyboard driver
    > Jun 2 11:26:19 localhost kernel: Initializing USB Mass Storage driver...
    > Jun 2 11:26:19 localhost kernel: usb.c: registered new driver usb-storage
    > Jun 2 11:26:19 localhost kernel: USB Mass Storage support registered.
    > Jun 2 11:26:19 localhost kernel: MIDI Loopback device driver
    > Jun 2 11:29:10 localhost kernel: hub.c: new USB device 00:04.2-2,
    > assigned address 3
    > Jun 2 11:29:10 localhost kernel: usb.c: USB device 3 (vend/prod
    > 0x54c/0x10) is not claimed by any active driver.
    >
    >
    >
    > > Jun 2 07:51:12 localhost kernel: ohci_hcd 0000:00:02.1: wakeup
    > > Jun 2 07:51:12 localhost kernel: usb 2-3: new full speed USB device
    > > using ohci_hcd and address 3
    > > Jun 2 07:51:13 localhost kernel: Initializing USB Mass Storage driver...
    > > Jun 2 07:51:13 localhost kernel: scsi0 : SCSI emulation for USB Mass
    > > Storage devices
    > > Jun 2 07:51:13 localhost kernel: usbcore: registered new driver usb-storage
    > > Jun 2 07:51:13 localhost kernel: USB Mass Storage support registered.
    > > Jun 2 07:51:13 localhost kernel: usb-storage: device found at 3
    > > Jun 2 07:51:13 localhost kernel: usb-storage: waiting for device to
    > > settle before scanning
    > > Jun 2 07:51:13 localhost usb.agent[27261]: usb-storage: loaded
    > > successfully
    > > Jun 2 07:51:13 localhost usb.agent[27261]: libgphoto2: loaded successfully
    > > Jun 2 07:51:18 localhost kernel: Vendor: OLYMPUS Model:
    > > C4100Z/C4000Z Rev: 1.00
    > > Jun 2 07:51:18 localhost kernel: Type: Direct-Access
    > > ANSI SCSI revision: 02
    > > Jun 2 07:51:18 localhost kernel: usb-storage: device scan complete
    > > Jun 2 07:51:18 localhost kernel: SCSI device sda: 256000 512-byte
    > > hdwr sectors (131 MB)
    > > Jun 2 07:51:18 localhost kernel: sda: assuming Write Enabled
    >
    > That is the message I'm missing. I don't know why it didn't show in my screen.
    > I restarted modutils and the following error message has come up my
    > screen (hope it helps somehow):
    >
    > # /etc/init.d/modutils restart
    > Calculating module dependencies...done.
    > Loading modules: usb-uhci
    > /lib/modules/2.4.27-2-k7/kernel/drivers/usb/host/usb-uhci.o:
    > init_module: No such device
    > Hint: insmod errors can be caused by incorrect module parameters,
    > including invalid IO or IRQ parameters.
    > You may find more information in syslog or the output from dmesg
    > /lib/modules/2.4.27-2-k7/kernel/drivers/usb/host/usb-uhci.o: insmod
    > /lib/modules/2.4.27-2-k7/kernel/drivers/usb/host/usb-uhci.o failed
    > /lib/modules/2.4.27-2-k7/kernel/drivers/usb/host/usb-uhci.o: insmod
    > usb-uhci failed
    > input usbkbd keybdev ntfs 3c59x usb-storage agpgart parport v_midi
    >
    > Moreover, I "modprobed" the sd_mod (though I'm not sure how it works).
    >
    > > Jun 2 07:51:18 localhost kernel: sda: assuming drive cache: write through
    > > Jun 2 07:51:18 localhost kernel: SCSI device sda: 256000 512-byte
    > > hdwr sectors (131 MB)
    > > Jun 2 07:51:18 localhost kernel: sda: assuming Write Enabled
    > > Jun 2 07:51:18 localhost kernel: sda: assuming drive cache: write through
    > > Jun 2 07:51:18 localhost kernel: /dev/scsi/host0/bus0/target0/lun0: p1
    > > Jun 2 07:51:18 localhost kernel: Attached scsi removable disk sda at
    > > scsi0, channel 0, id 0, lun 0
    > > Jun 2 07:51:18 localhost scsi.agent[27430]: sd_mod: loaded
    > > sucessfully (for disk)
    > > Jun 2 07:51:19 localhost udev[27460]: creating device node '/dev/sda'
    > > Jun 2 07:51:19 localhost udev[27471]: creating device node '/dev/sda1'
    > >
    > > telling me that the camera is at /dev/sda1
    >
    > No it's not....actually i think it is not at anywhere here. :(
    >
    > Thanks you all,
    >
    > Romulo
    >
    > > Chers
    > >
    > > Adam
    > >
    > >

    What does cat /proc/partitions show?

    If it assigned the drive to e.g. sdb
    and found a valid partition table, you
    would see e.g. sdb1

    -- Tony Godshall 

    -- 
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
  • Next message: Winston Smith: "Re: excluding files w/ tar"

    Relevant Pages

    • Re: HP USB Mass Storage device issue
      ... deals with scsi stuff. ... Still no dectection of the usb flash drive size in the syslog with the ... > driver for your harddisk should be there (don't recall its ... > - if not, detach, insmod manually, attach ...
      (Debian-User)
    • Re: syslog loves the new driver core code
      ... On Thu, 31 Mar 2005, Greg KH wrote: ... > stuff in the syslog for every device it tries to match up with a driver ... > syslog when we have a real error. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Lockup
      ... >> things,too.Like the nvidia driver and harassing different forums ... insmod errors can be caused by incorrect module parameters, ... > This is with alsa 0.9 from woody. ... recompile my kernel leaving everything without any drivers for sound ...
      (Debian-User)
    • Re: Beginning usb
      ... The above messages wouldn't show up in syslog ... OHCI chipset instead of UHCI and that it's driver is loaded.) ... > sda: Write Protect is off ...
      (comp.os.linux.misc)
    • RE: RAID monitoring
      ... Configuring syslog to email you would probably be the easiest thing to do. ... The mly driver does have the capability to post diagnostic information. ... > The Global Array Manager software that they have works with SCO Unix, ...
      (freebsd-questions)