LinuxQuestions.org - usb stick connecting / disconnecting

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - usb stick connecting / disconnecting (https://www.linuxquestions.org/questions/slackware-14/usb-stick-connecting-disconnecting-599629/)

usb stick connecting / disconnecting

Hi everyone
I have installed slack 12 on my box and have found that my usb stick and camera act very strangely (on kde), they connect for +/10 - 20 seconds then they drop with kde popping up a new window saying its found a new usb device, The following is my output of dmesg. Has anyone had the same problem? any ideas to solve it will be much appreciated.

Thanks

JP

usb-storage: device found at 37
usb-storage: waiting for device to settle before scanning
kobject_add failed for usb_storage with -EEXIST, don't try to register things with the same name in the same directory.
[<c03e86f7>] kobject_shadow_add+0x117/0x1a0
[<c013fba4>] mod_sysfs_setup+0x24/0xb0
[<c0141458>] sys_init_module+0x1648/0x1940
[<c0102ae8>] syscall_call+0x7/0xb
=======================
kobject_add failed for usb_storage with -EEXIST, don't try to register things with the same name in the same directory.
[<c03e86f7>] kobject_shadow_add+0x117/0x1a0
[<c013fba4>] mod_sysfs_setup+0x24/0xb0
[<c0141458>] sys_init_module+0x1648/0x1940
[<c0102ae8>] syscall_call+0x7/0xb
=======================
scsi 33:0:0:0: Direct-Access JetFlash TS512MJF160 0.00 PQ: 0 ANSI: 2
SCSI device sdb: 1024000 512-byte hdwr sectors (524 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 00 00 00
sdb: assuming drive cache: write through
SCSI device sdb: 1024000 512-byte hdwr sectors (524 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 00 00 00
sdb: assuming drive cache: write through
sdb: sdb1
sd 33:0:0:0: Attached scsi removable disk sdb
sd 33:0:0:0: Attached scsi generic sg1 type 0
usb-storage: device scan complete
usb 1-5: USB disconnect, address 37
bash-3.1#

From those "-EEXIST" entries it looks like you're still using the huge-smp kernel. It's recommended to change to the generic-smp kernel after installation. Don't know for sure if this will solve your problem. Read the CHANGES_AND_HINTS.TXT and the README.initrd in /boot.

Quote:

usb 1-5: USB disconnect, address 37

This line makes me think that there is a loose connection there somewhere. But yeah, make sure you try with generic kernel first.

It's the kernel. Patrick did something he shouldn't have and the huge-smp kernel was built with a different configuration than the modules package was (feel free to check this yourself if you doubt). ...the result being that part of the USB code (particularly parts relating to mass-storage) is directly in the kernel as well as in the modules, which means a module gets loaded when it's supposed to be, there's a symbol collision, and the whole mess goes down in flames.

There's a reason people are told to do a make mrproper if they reconfig something from the core kernel to be a module or vice-versa, and this is it.

Rebuilding the huge-smp kernel and it's modules cleanly makes this problem go away.

Hi,

Did you read the 'CHANGES_AND_HINTS.TXT'?

Code:

excerpt from CHANGES_AND_HINTS.TXT;



As stated earlier, it is recommended that you use one of the generic kernels

  rather than the huge kernels; the huge kernel is primarily intended as 

  an "installer" and "emergency" kernel in case you forget to make an initrd.

  However, if you do use one of the huge kernels, you will likely encounter 

  errors like this:

    kobject_add failed for uhci_hcd with -EEXIST, don't try to register

  These occur because the respective drivers are compiled statically into the

  huge kernels but udev tries to load them anyway.  These errors should be safe

  to ignore, but if you really don't want them to appear, you can blacklist the

  modules that try to load in /etc/modprobe.d/blacklist.  However, make sure you

  remove them from the blacklist if you ever decide to use the (recommended)

  generic kernels.

Weird thing is , I never had such a problem with the slack11 DVD included huge kernel (2.6 ) ... why is this popping up now in slack 12 ?