On Fri, 10 Aug 2007, Michael Habashy wrote:
Note: please don't top post, it makes it hard to read and follow threads
But how do you know that ? it is /dev/sdb ??? this is what is driving me up
a wall.
it puts these things in the log.
I got a whole mess of strange devices in the /dev directory.
And if i download a utility..it tells me everything...except what i want to
hear...
it is plain crazy.
mjh
On 8/10/07, Marko Randjelovic <[EMAIL PROTECTED]> wrote:
Michael Habashy wrote:
To all -- I would appriciate any help...
Everytime i insert a usb device on my server....i get similar messeges
like
the ones below:
Aug 10 11:28:18 rider kernel: usb 1-4: USB disconnect, address 4
Aug 10 11:28:41 rider kernel: usb 2-8: new full speed USB device using
ohci_hcd and address 4
Aug 10 11:28:42 rider kernel: usb 2-8: configuration #1 chosen from 1
choice
Aug 10 11:30:39 rider kernel: usb 2-8: USB disconnect, address 4
Aug 10 11:30:48 rider kernel: usb 2-8: new full speed USB device using
ohci_hcd and address 5
Aug 10 11:30:48 rider kernel: usb 2-8: configuration #1 chosen from 1
choice
Aug 10 11:47:57 rider -- MARK --
Aug 10 09:06:35 rider kernel: usb 2-4: USB disconnect, address 3
Aug 10 09:07:30 rider kernel: usb 1-4: new high speed USB device using
ehci_hcd and address 4
Aug 10 09:07:31 rider kernel: usb 1-4: configuration #1 chosen from 2
choices
Aug 10 09:07:31 rider kernel: Initializing USB Mass Storage driver...
Aug 10 09:07:31 rider kernel: scsi6 : SCSI emulation for USB Mass
Storage
devices
Aug 10 09:07:31 rider kernel: usbcore: registered new driver usb-storage
I further get some devices showing up in /dev directory like:
usbdev1.1_ep00 usbdev1.7_ep02 usbdev2.1_ep00 usbdev2.2_ep02
usbdev2.2_ep82 usbdev2.5_ep03
usbdev1.1_ep81 usbdev1.7_ep81 usbdev2.1_ep81 usbdev2.2_ep03
usbdev2.2_ep83 usbdev2.5_ep81
I can not seem to access them or do anything with them. Is there a
document
on how debian 4.0 deals with usb devices?
Somehting that wll help me through this jigsaw puzzle that i got myself
into
?
thanks
mjh
My MP3 player is on /dev/sdb, since sda is SATA HDD.
It looks like you machine is finding the device and if you look further
into the log, you will see where it gets its device name. Here I just
plugged in a usb key:
Aug 10 10:15:31 proto kernel: usb 3-4.3: new high speed USB device using
ehci_hcd and address 7
Aug 10 10:15:31 proto kernel: usb 3-4.3: configuration #1 chosen from 1
choice
Aug 10 10:15:31 proto kernel: scsi7 : SCSI emulation for USB Mass Storage
devices
Aug 10 10:15:31 proto kernel: usb-storage: device found at 7
Aug 10 10:15:31 proto kernel: usb-storage: waiting for device to settle
before scanning
Aug 10 10:15:36 proto kernel: Vendor: SanDisk Model: Cruzer Mini
Rev: 0.4
Aug 10 10:15:36 proto kernel: Type: Direct-Access
ANSI SCSI revision: 02
Aug 10 10:15:36 proto kernel: SCSI device sdf: 4001760 512-byte hdwr
sectors (2049 MB)
Aug 10 10:15:36 proto kernel: sdf: Write Protect is off
Aug 10 10:15:36 proto kernel: sdf: Mode Sense: 03 00 00 00
Aug 10 10:15:36 proto kernel: sdf: assuming drive cache: write through
Aug 10 10:15:36 proto kernel: SCSI device sdf: 4001760 512-byte hdwr
sectors (2049 MB)
Aug 10 10:15:36 proto kernel: sdf: Write Protect is off
Aug 10 10:15:36 proto kernel: sdf: Mode Sense: 03 00 00 00
Aug 10 10:15:36 proto kernel: sdf: assuming drive cache: write through
Aug 10 10:15:36 proto kernel: sdf: sdf1
so we see that it gets assigned to /dev/sdf with a partition at sdf1. Then
you can mount /dev/sdf1 to where ever you like. Alternatively you can
install the usbmount package, and it will auto mount usb devices as they
get found as well.
-+-
8 out of 10 Owners who Expressed a Preference said Their Cats Preferred Techno.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
