Re: usb vs. drivers

From: Christian Convey (conveycj_at_npt.nuwc.navy.mil)
Date: 11/30/04

  • Next message: Juha Jäykkä: "problems waking up from S3"
    Date: Tue, 30 Nov 2004 09:23:39 -0500
    To: debian-user <debian-user@lists.debian.org>
    
    

    Hi Andrea,

    I am using hotplug and udev. Thanks for the Gnome tips; I'd still like
    to solve this at a lower level if possible.

    Do you know the process by which the system goes from (a) discovering
    that a device was connected to a USB port, to (z) binding a driver to
    that device?

    The reason I'm asking is that I'm trying to make my camera work on
    Sarge. I *suspect* that no driver is getting loaded for it. I figure
    that understanding the process by which drivers get bound to hotplugged
    devices will let me better debug the problem.

    Thanks for your help,
    Christian

    Andrea Vettorello wrote:
    > On Tue, 30 Nov 2004 08:44:57 -0500, Christian Convey
    > <conveycj@npt.nuwc.navy.mil> wrote:
    >
    >>Hey guys,
    >>
    >>I've got a usb camera (Kodak DX6490). I'm starting to suspect from
    >>various tinkering I've done (in Knoppix, FC3, and Sarge) that the kernel
    >>can't find a module to associate with the camera, and that's causing my
    >>problems.
    >>
    >>In 2.6/Sarge...
    >>- How does the kernel know which driver to use for a USB device I plug in?
    >>
    >
    >
    > The kernel alone do nothing, you need "userland" programs to load
    > kernel modules when a new HD is plugged, like the "hotplug" package.
    >
    > If you only need to access the photos, usually you only need to load
    > the "usb-storage" kernel module and maybe the "fat" or "vfat".
    >
    > If you use Gnome, and you install "udev", "hal",
    > "gnome-volume-manager" and "hotplug", you usually end with a nice icon
    > on the desktop automagically whenever you attach a USB mass storage to
    > your pc, and digital cameras can be seen like USB mass storage.
    >
    >
    >>- What's the easiest reliable way of knowing whether or not the kernel
    >>managed to bind a driver to a USB device I plug in?
    >>
    >
    >
    > Looking in your /varl/log/syslog or perusing your /proc/bus/usb or
    > /sys/bus/sys. There are utilities that do this for you and show a nice
    > tree with device informations.
    >
    >
    > Andrea
    >
    >

    -- 
    Christian Convey
    Computer Scientist,
    Naval Undersea Warfare Center
    Newport, RI
    -- 
    To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
    

  • Next message: Juha Jäykkä: "problems waking up from S3"

    Relevant Pages

    • Mounting a digital camera
      ... camera on my RH 8.0 machine. ... "Initializing USB Mass Storage driver... ... correctly mount my camera? ...
      (comp.os.linux.hardware)
    • Re: [RFC/PATCH 0/22] W1: sysfs, lifetime and other fixes
      ... It is not hotplug, and your changes broke it completely. ... > - separate master registering and allocation so drivers can setup proper ... > Drop custom-made hotplug over netlink notification from w1 core. ... > - get rid of separate refcount, rely on driver model to enforce ...
      (Linux-Kernel)
    • uevent buffer overflow in input layer
      ... mounted filesystem with ordered data mode. ... Real Time Clock Driver v1.12ac ... Probing IDE interface ide0... ... Initializing USB Mass Storage driver... ...
      (Linux-Kernel)
    • Sound card not working
      ... PCI: PCI BIOS revision 2.10 entry at 0xfb4d0, ... ACPI tables contain no PCI IRQ routing entries ... RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize ... Initializing USB Mass Storage driver... ...
      (Debian-User)
    • Re: help needed with HP cdwriter 8200 plus
      ... Copyright 1995-2000 Jörg Schilling Linux sg driver version: ... Starting to write CD/DVD at speed 2 in dummy mode for single session. ... usb-storage scsi0: SCSI emulation for USB Mass Storage devices Vendor: HP ... localhost last message repeated 3 times May 28 18:59:14 localhost kernel: ...
      (comp.os.linux.hardware)