VectorLinux

Vectorbie Station => Vectorbie Questions => Topic started by: bobbear43 on September 15, 2007, 12:08:13 pm

Title: Long Time to Read USB JumpDrive
Post by: bobbear43 on September 15, 2007, 12:08:13 pm
I am working on getting a network card up and other things, and have to transfer many files from my Windoze desktop to my laptop with VL. VL has no problem mounting the drive, but when I open it on the desktop it takes a LONG time sometimes for the file list to appear. Other times it is immediate. Am I missing something here?

Is the card accessible from the command line as well?
Title: Re: Long Time to Read USB JumpDrive
Post by: easuter on September 15, 2007, 01:36:48 pm
Firstly version of VectorLinux are you using?

You may also try using this command in a terminal to examine the kernel messages when the device is plugged in or removed:
(you will need to be root for this)

Code: [Select]
tail -f /var/log/messages
Leave that command running in a terminal, and then unplug and re-insert your usb drive, each time waiting for the messages to stop before removing/re-inserting the device.
Then you can post the output here.

From those messages you should be able to see if errors are occurring, and if the correct usb driver is being used (uhci/ohci indicates usb 1.0, and ehci indicates usb 2.0).
Title: Re: Long Time to Read USB JumpDrive
Post by: bobbear43 on September 16, 2007, 11:27:05 am
VL 5.8 Standard. The Thinkpad 600E only has USB 1.0 support.

The device only lights up when it is present at boot. If it is subsequently removed and reinserted, it is not active. If it is not present at boot, it cannot be accessed if inserted after boot.

Here is tail output when inserted after boot:
root:# tail -f /var/log/messages
Sep 18 11:05:58 vector vl-hot_umount: devname: sda
Sep 18 11:05:58 vector vl-hot_umount: mountbase: sda
Sep 18 11:05:58 vector vl-hot_umount: volname: vol
Sep 18 11:05:58 vector vl-hot_umount: /mnt/vl-hot/sda/vol
Sep 18 11:05:58 vector vl-hot_umount: /mnt/vl-hot/sda/vol not mounted, deleting /mnt/vl-hot/sda/vol and desktop icons
Sep 18 11:05:58 vector vl-hot_umount: Deleting desktop file vl-hot-sda-vol.desktop
Sep 18 11:05:58 vector vl-hot_umount: No partitions remaining, rmdir /mnt/vl-hot/sda/
Sep 18 11:05:58 vector vl-hot_umount: Finishing vl-umount...
Sep 18 11:22:01 vector -- MARK --
Sep 18 11:42:01 vector -- MARK --

Here is tail output when present at boot, subsequently removed and reinserted; resinsert is not detected:
root:# tail -f /var/log/messages
Sep 18 12:00:56 vector ifplugd(ath0)[3681]: Initialization complete, link beat not detected.
Sep 18 12:00:57 vector ifplugd(eth0)[3675]: Using interface eth0
Sep 18 12:00:58 vector ifplugd(eth0)[3675]: Failed to detect plug status of eth0Sep 18 12:00:58 vector ifplugd(eth0)[3675]: Exiting.
Sep 18 12:01:03 vector /usr/sbin/gpm[4502]: *** info [startup.c(95)]:
Sep 18 12:01:03 vector /usr/sbin/gpm[4502]: Started gpm successfully. Entered daemon mode.
Sep 18 12:01:07 vector vl-hot_mount: /dev/vl-hot/sda1 Filesystem is FAT16
Sep 18 12:01:07 vector vl-hot_mount: mounting FAT16 filesystem: /dev/vl-hot/sda1 on /mnt/vl-hot/sda/vol1
Sep 18 12:01:33 vector vl-hot_mount: Showing desktop file vl-hot-sda-vol1.desktop
Sep 18 12:01:33 vector vl-hot_mount: Finishing vl-hot_mount...
Sep 18 12:07:42 vector kernel: usb 1-1: USB disconnect, address 2
Sep 18 12:07:42 vector vl-hot_umount: Starting vl-hot_umount...
Sep 18 12:07:42 vector vl-hot_umount: devname: sda1
Sep 18 12:07:42 vector vl-hot_umount: mountbase: sda
Sep 18 12:07:42 vector vl-hot_umount: volname: vol1
Sep 18 12:07:42 vector vl-hot_umount: /mnt/vl-hot/sda/vol1
Sep 18 12:07:42 vector vl-hot_umount: umounting /mnt/vl-hot/sda/vol1
Sep 18 12:07:42 vector vl-hot_umount: Deleting desktop file vl-hot-sda-vol1.desktop
Sep 18 12:07:43 vector vl-hot_umount: removing /mnt/vl-hot/sda/vol1
Sep 18 12:07:43 vector vl-hot_umount: No partitions remaining, rmdir /mnt/vl-hot/sda/
Sep 18 12:07:43 vector vl-hot_umount: Finishing vl-umount...
Sep 18 12:07:43 vector vl-hot_umount: Starting vl-hot_umount...
Sep 18 12:07:43 vector vl-hot_umount: devname: sda
Sep 18 12:07:43 vector vl-hot_umount: mountbase: sda
Sep 18 12:07:43 vector vl-hot_umount: volname: vol
Sep 18 12:07:43 vector vl-hot_umount: /mnt/vl-hot/sda/vol
Sep 18 12:07:43 vector vl-hot_umount: /mnt/vl-hot/sda/vol not mounted, deleting /mnt/vl-hot/sda/vol and desktop icons
Sep 18 12:07:43 vector vl-hot_umount: Deleting desktop file vl-hot-sda-vol.desktop
Sep 18 12:07:43 vector vl-hot_umount: No partitions remaining, rmdir /mnt/vl-hot/sda/
Sep 18 12:07:43 vector vl-hot_umount: Finishing vl-umount...
Title: Re: Long Time to Read USB JumpDrive
Post by: Joe1962 on September 18, 2007, 04:36:53 pm
Sounds like udev is only working during coldplug (during boot) and not later on.
Title: Re: Long Time to Read USB JumpDrive
Post by: bobbear43 on September 19, 2007, 03:15:42 pm
How do I fix that??? Or am I able to???
Title: Re: Long Time to Read USB JumpDrive
Post by: Joe1962 on September 19, 2007, 03:27:37 pm
You could check a couple of things first:

- run htop and see if there is a "/sbin/udevd --daemon" process running.
- open a root console and run udevmonitor, then plug in the drive and see if it detects it.
Title: Re: Long Time to Read USB JumpDrive
Post by: bobbear43 on September 20, 2007, 03:55:55 pm
htop: "/sbin/udevd --daemon" process is running
udevmonitor does not detect the insertion of the usb jump drive
Title: Re: Long Time to Read USB JumpDrive
Post by: Joe1962 on September 20, 2007, 04:05:44 pm
Ok, time for some real digging. If you can post here the output of lsmod, we might get further. Anybody else have any ideas?
Title: Re: Long Time to Read USB JumpDrive
Post by: bobbear43 on September 20, 2007, 04:28:52 pm
root:# lsmod
Module                  Size  Used by
xt_tcpudp               3968  4
xt_state                2816  7
iptable_mangle          3200  0
ipt_REJECT              4864  1
ip_nat_irc              3072  0
ip_conntrack_irc        6128  1 ip_nat_irc
ip_nat_ftp              3584  0
ip_conntrack_ftp        6640  1 ip_nat_ftp
iptable_nat             6660  0
ip_nat                 13868  3 ip_nat_irc,ip_nat_ftp,iptable_nat
ip_conntrack           37600  7 xt_state,ip_nat_irc,ip_conntrack_irc,ip_nat_ftp,ip_conntrack_ftp,iptable_nat,ip_nat
iptable_filter          3328  1
ip_tables              12020  3 iptable_mangle,iptable_nat,iptable_filter
x_tables               11140  5 xt_tcpudp,xt_state,ipt_REJECT,iptable_nat,ip_tables
cpufreq_conservative     6536  0
cpufreq_ondemand        5900  0
cpufreq_performance     2816  0
cpufreq_powersave       2560  0
speedstep_lib           4740  0
freq_table              4512  0
sg                     25500  0
fuse                   37780  0
snd_cs4236             15464  2
snd_opl3_lib            8960  1 snd_cs4236
snd_hwdep               7428  1 snd_opl3_lib
snd_cs4236_lib         14336  1 snd_cs4236
snd_mpu401_uart         7040  1 snd_cs4236
snd_cs4231_lib         19968  2 snd_cs4236,snd_cs4236_lib
snd_seq_dummy           3716  0
snd_seq_oss            27392  0
snd_seq_midi_event      6528  1 snd_seq_oss
snd_seq                42320  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_pcm_oss            37280  0
snd_mixer_oss          14080  3 snd_pcm_oss
wlan_scan_sta          12032  1
ath_rate_sample        11264  1
ath_pci                75936  0
wlan                  163524  4 wlan_scan_sta,ath_rate_sample,ath_pci
ath_hal               190672  3 ath_rate_sample,ath_pci
pcmcia                 22560  0
snd_cs46xx             72520  0
gameport               11912  1 snd_cs46xx
snd_rawmidi            18592  2 snd_mpu401_uart,snd_cs46xx
snd_seq_device          6924  5 snd_opl3_lib,snd_seq_dummy,snd_seq_oss,snd_seq,snd_rawmidi
snd_ac97_codec         80160  1 snd_cs46xx
snd_ac97_bus            3072  1 snd_ac97_codec
snd_pcm                61828  5 snd_cs4236_lib,snd_cs4231_lib,snd_pcm_oss,snd_cs46xx,snd_ac97_codec
shpchp                 29604  0
snd_timer              18692  4 snd_opl3_lib,snd_cs4231_lib,snd_seq,snd_pcm
snd                    39780  16 snd_cs4236,snd_opl3_lib,snd_hwdep,snd_cs4236_lib,snd_mpu401_uart,snd_cs4231_lib,snd_seq_oss,snd_seq,snd_pcm_oss,snd_mixer_oss,snd_cs46xx,snd_rawmidi,snd_seq_device,snd_ac97_codec,snd_pcm,snd_timer
yenta_socket           22156  3
rsrc_nonstatic         10624  1 yenta_socket
soundcore               8032  3 snd
pcmcia_core            31512  3 pcmcia,yenta_socket,rsrc_nonstatic
evdev                   8320  0
snd_page_alloc          8072  3 snd_cs4231_lib,snd_cs46xx,snd_pcm
i2c_piix4               8076  0
serio_raw               6148  0
pcspkr                  3456  0
intel_agp              19100  1
i2c_core               16256  1 i2c_piix4
vector:/~
root:#
Title: Re: Long Time to Read USB JumpDrive
Post by: newt on September 20, 2007, 04:41:09 pm
I don't know if either of these suggestions would help your situation or not, but they may be worth a try. 1) Make sure you're running the latest vl-hot from the repo; I know there's a newer one than what came with VL58Standard, and 2) You could try formatting the flash drive so that you know you're working with a fresh, clean drive.  Again, I don't know if either suggestion would help ???
Title: Re: Long Time to Read USB JumpDrive
Post by: Joe1962 on September 20, 2007, 04:53:08 pm
Good suggestions, but only after we get udevmonitor to "say" something.


EDIT: Ok, should have said this together with the udevmonitor post, but better late than never: leave "tail -f /var/log/messages" running in a console and then plug in the drive, post any output.
Title: Re: Long Time to Read USB JumpDrive
Post by: hata_ph on September 20, 2007, 05:58:13 pm
post your lspci and lsusb too......
Title: Re: Long Time to Read USB JumpDrive
Post by: Joe1962 on September 20, 2007, 06:06:19 pm
Thanks, hata_ph. My mind's all over the place tonight... ::)
Title: Re: Long Time to Read USB JumpDrive
Post by: hata_ph on September 20, 2007, 06:13:49 pm
Thanks, hata_ph. My mind's all over the place tonight... ::)

Is ok...I know the feeling too...
Title: Re: Long Time to Read USB JumpDrive
Post by: bobbear43 on September 21, 2007, 09:53:57 am
device was present at boot; tail output in prior post above. i guess it might be important to restate what problem i am working on. 1) sometimes long time to read the card when opening the file system for it 2) never recognized unless present at boot; not recognized if removed or inserted after boot, except to unmount it if removed when present at boot.

suggestion to format the drive: i believe that would remove the information Windoze uses on load to recognize it; would remove the "system information" folder.

root:# lspci
00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)
00:02.0 CardBus bridge: Texas Instruments PCI1251A
00:02.1 CardBus bridge: Texas Instruments PCI1251A
00:06.0 Multimedia audio controller: Cirrus Logic CS 4610/11 [CrystalClear SoundFusion Audio Accelerator] (rev 01)
00:07.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02)
00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
00:07.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02)
01:00.0 VGA compatible controller: Neomagic Corporation NM2200 [MagicGraph 256AV] (rev 12)
02:00.0 Ethernet controller: Atheros Communications, Inc. AR5005G 802.11abg NIC (rev 01)
vector:/~
root:# lsusb
Bus 1 Device 1: ID 0000:0000
Bus 1 Device 2: ID 05dc:a400 Lexar Media, Inc.
Title: Re: Long Time to Read USB JumpDrive
Post by: hata_ph on September 21, 2007, 10:10:17 am
Quote
Bus 1 Device 2: ID 05dc:a400 Lexar Media, Inc.

is that your USB JumpDrive or other USB device plug in while checking the lsusb?

btw, did you have another USB pendrive to test the performance?
Title: Re: Long Time to Read USB JumpDrive
Post by: rbistolfi on September 21, 2007, 10:16:17 am
a long shot about the mount issue, just an idea to be evaluated by the experts, could be a permissions problem? May be the jumpdrive is mounted at boot time because that is done by the root user, same problem has been reported with the usb cameras and other serial devices. That never happened with a jumpdrive, but may be this one is special.
Title: Re: Long Time to Read USB JumpDrive
Post by: newt on September 21, 2007, 11:51:16 am
suggestion to format the drive: i believe that would remove the information Windoze uses on load to recognize it; would remove the "system information" folder.
I should have qualified that suggestion with: "Backup your data first!!! because it will be lost".  Aside from that, there shouldn't be a 'system information' folder on the drive.  I have a couple flash drives that I use to move data from win to nix to osx and neither have a 'system information' folder.  Has your flash drive ever been loaded with a live version of winXP, or U3 software?  If yes then I think you will definitely be wanting to scrub the drive clean.  I've specifically read about the "pain" that can be caused from the U3 software, and the troubles to remove all of the remnants of the U3 app.

1) sometimes long time to read the card when opening the file system for it
I would hope that it's related to the mounting/umounting issue and that by fixing the issue would alleviate this problem, but you never know.

2) never recognized unless present at boot; not recognized if removed or inserted after boot, except to unmount it if removed when present at boot.
Back to basics on this one.  Reboot your system without the flash drive attached.  Once booted, insert the flash drive (the expectation is that it will not be automatically mounted).  Then run lsusb - can you identify the device?  If yes, can you then manually mount the drive?  If no, then (guru needed) is there a manual way to force a recheck of the USB hubs or all connected hardware (udev function??).
Title: Re: Long Time to Read USB JumpDrive
Post by: bobbear43 on September 21, 2007, 02:29:47 pm
response to hata_ph:
the lsusb output was with the usb drive present at boot; if inserted after boot, lsusb returns: Bus 1 Device 1 : ID 0000:0000 --- nothing there.
right now I do not have another usb jump drive but i can check and see if the usb ethernet NIC i have is recognized when it is inserted.

response to newtor:
will try reformatting the drive and see if that improves performance. it has never had xp or u3 on it .... just files to exchange between computers when couldn't network to do that.
if device is not present at boot and it is subsequently inserted, lsusb returns: Bus 1 Device 1 : ID 0000:0000 --- nothing there, as in response to hata_ph.
i have no idea how to manually mount the drive. instructions on that please?
Title: Re: Long Time to Read USB JumpDrive
Post by: newt on September 21, 2007, 03:19:37 pm
Thanks for the info.  I think Joe was correct in his thinking that the device is only being polled at boot time and not during runtime.  Someone else mentioned this also, but do you happen to have anything else that's usb that you could test lsusb with? A keyboard, mouse, extra flash drive, webcam, anything?  Just something that you could try plugging in during runtime to see if lsmod displays the appropriate device info.

Check out 'man mount' for more info on syntax and other options, but an example for a flash drive would be:
mount -t vfat /dev/sda1 /home/<mount_point>

...where <mount_point> is an empty directory in your /home directory.  However, since udev does not pick up your flash drive during runtime then (technically) sda1 should not be created and thus not available for mounting.

Here is some further reading on manually mounting your drive: http://linuxhelp.blogspot.com/2007/03/steps-to-manually-mount-usb-flash-drive.html

Good luck!
Title: Re: Long Time to Read USB JumpDrive
Post by: GrannyGeek on September 21, 2007, 06:55:10 pm
This trick from Joe 1962 enabled me to get a media card recognized when I used my built-in media card reader. Insert the device and as root at a terminal prompt, type
sginfo -l

After I do that, VL recognizes the card and puts an icon on the desktop.

If you don't get an icon for your drive, run fdisk -l as root in a terminal and see if it's listed. If so, you should be able to mount it manually as root.

I don't know if this will help your situation, but it wouldn't hurt to try.
--GrannyGeek