Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place! |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
|
12-21-2009, 09:26 PM
|
#16
|
Member
Registered: Oct 2004
Location: Atlanta
Distribution: CentOS, RHEL, HP-UX, OS X
Posts: 567
Rep:
|
Why don't you just plug in the drive and then tail the dmesg. Like this
|
|
|
12-21-2009, 11:47 PM
|
#17
|
Member
Registered: Aug 2009
Posts: 228
Original Poster
Rep:
|
Quote:
Originally Posted by linuxlover.chaitanya
Its not showing what the device is recognized as. Post the output without grep.
It should show something like this:
Code:
[28727.437375] sd 4:0:0:0: Attached scsi generic sg1 type 0
[28727.438886] sd 4:0:0:0: [sdb] 15679488 512-byte logical blocks: (8.02 GB/7.47 GiB)
[28727.439489] sd 4:0:0:0: [sdb] Write Protect is off
[28727.439493] sd 4:0:0:0: [sdb] Mode Sense: 23 00 00 00
[28727.439496] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[28727.444246] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[28727.444254] sdb: sdb1
[28727.604384] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[28727.604390] sd 4:0:0:0: [sdb] Attached SCSI removable disk
|
Please find attached the dmesg output .
|
|
|
12-21-2009, 11:56 PM
|
#18
|
Member
Registered: Aug 2009
Posts: 228
Original Poster
Rep:
|
Quote:
Originally Posted by evo2
I wonder if you have the needed kernel moudles. Can you please post the output of
Code:
lsmod | grep -E 'usb|scsi'
Evo2.
|
Please find below the requested output :
[root@mss-0 ~]# lsmod |grep -E 'usb|scsi'
xpp_usb 21064 0
xpp 135748 1 xpp_usb
wcusb 18176 0
zaptel 190980 11 ztdummy,xpp,wcusb,wctdm,wcfxo,wctdm24xxp,wcte11xp,wct1xxp,wcte12xp,wct4xxp,tor2
scsi_mod 134605 2 libata,sd_mod
|
|
|
12-22-2009, 12:09 AM
|
#19
|
Member
Registered: Aug 2009
Posts: 228
Original Poster
Rep:
|
Quote:
Originally Posted by worm5252
Why don't you just plug in the drive and then tail the dmesg. Like this
|
Please find below the output of "dmesg |tail" :
[root@mss-0 ~]# dmesg |tail
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
Bluetooth: HIDP (Human Interface Emulation) ver 1.1
eth0: link up, 100Mbps, full-duplex
eth0: no IPv6 routers present
|
|
|
12-22-2009, 12:24 AM
|
#20
|
LQ Guru
Registered: Jan 2009
Location: Japan
Distribution: Mostly Debian and CentOS
Posts: 6,726
|
Quote:
Originally Posted by hadimotamedi
Please find below the requested output :
[root@mss-0 ~]# lsmod |grep -E 'usb|scsi'
xpp_usb 21064 0
xpp 135748 1 xpp_usb
wcusb 18176 0
zaptel 190980 11 ztdummy,xpp,wcusb,wctdm,wcfxo,wctdm24xxp,wcte11xp,wct1xxp,wcte12xp,wct4xxp,tor2
scsi_mod 134605 2 libata,sd_mod
|
You seem to be missing the required drivers. Please run the following
command to add the usb_storage module into the running kernel:
Code:
modprobe usb_storage
Now try inserting your usb stick again, and then look at the output of dmesg.
HTH,
Evo2.
|
|
|
12-22-2009, 01:08 AM
|
#21
|
Member
Registered: Aug 2009
Posts: 228
Original Poster
Rep:
|
Quote:
Originally Posted by evo2
You seem to be missing the required drivers. Please run the following
command to add the usb_storage module into the running kernel:
Code:
modprobe usb_storage
Now try inserting your usb stick again, and then look at the output of dmesg.
HTH,
Evo2.
|
Please find attached the dmesg output after issuing the "modprobe usb_storage" .
|
|
|
12-22-2009, 01:32 AM
|
#22
|
LQ Guru
Registered: Jan 2009
Location: Japan
Distribution: Mostly Debian and CentOS
Posts: 6,726
|
Quote:
Originally Posted by hadimotamedi
Please find attached the dmesg output after issuing the "modprobe usb_storage" .
|
Did you reinsert the USB thumb driver after runing modprobe and before running dmesg?
Evo2.
|
|
|
12-22-2009, 01:57 AM
|
#23
|
Member
Registered: Aug 2009
Posts: 228
Original Poster
Rep:
|
Quote:
Originally Posted by evo2
Did you reinsert the USB thumb driver after runing modprobe and before running dmesg?
Evo2.
|
Yes , I did .
|
|
|
12-22-2009, 08:31 PM
|
#24
|
LQ Guru
Registered: Jan 2009
Location: Japan
Distribution: Mostly Debian and CentOS
Posts: 6,726
|
Quote:
Originally Posted by hadimotamedi
Yes , I did .
|
Hmm, this is a little strange.
Can you please post the output of
Code:
cat /proc/bus/usb/devices
Cheers,
Evo2.
|
|
|
All times are GMT -5. The time now is 06:34 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|