Unix Technical Forum

S12 and USB, stock kernel 2.6.21.5-smp #2 SMP

This is a discussion on S12 and USB, stock kernel 2.6.21.5-smp #2 SMP within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> In Slackware 12, when inserting a USB stick, the device /dev/sda,b,c,d etc, are no longer created as they had ...


Go Back   Unix Technical Forum > Unix Operating Systems > Slackware Linux Support

Register FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 02-21-2008, 04:34 AM
Peter
 
Posts: n/a
Default S12 and USB, stock kernel 2.6.21.5-smp #2 SMP

In Slackware 12, when inserting a USB stick, the device /dev/sda,b,c,d
etc, are no longer created as they had been under Slack 11. Therefore,
using USB sticks, cf cards, etc. is not possible.

My scanner and printer show up with lsusb, but the stick or multi-device
unit for CF cards do not.

udev and hal are being loaded. I noticed this bug

https://bugs.launchpad.net/ubuntu/+s....20/+bug/88746

In addition, when using my scanner via VMWare (not sane compatible), there
is a tremendous delay when scanning -- almost like an interrupt conflict
or problem. This did not occur under S11.

I wanted to know if anyone else has had this or a similar issue. dmesg
does not show anything obvious other then this sequence of messages:

shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Linux agpgart interface v0.102 (c) Dave Jones
kobject_add failed for uhci_hcd 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 uhci_hcd 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 uhci_hcd 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 uhci_hcd 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
=======================
agpgart: Detected AGP bridge 0
agpgart: AGP aperture is 128M @ 0xd0000000
kobject_add failed for ehci_hcd 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
=======================
ieee1394: exports duplicate symbol _csr1212_destroy_keyval (owned by
kernel)
......
hdc: lost interrupt
hdc: lost interrupt

(hdc=cdrom)

Anyone else have this issue? Link to additional information?

TIA
--
Peter
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old 02-21-2008, 04:34 AM
Eric Hameleers
 
Posts: n/a
Default Re: S12 and USB, stock kernel 2.6.21.5-smp #2 SMP

Peter wrote:
> In Slackware 12, when inserting a USB stick, the device /dev/sda,b,c,d
> etc, are no longer created as they had been under Slack 11. Therefore,
> using USB sticks, cf cards, etc. is not possible.
>
> My scanner and printer show up with lsusb, but the stick or multi-device
> unit for CF cards do not.
>
> udev and hal are being loaded. I noticed this bug


On my fresh install of Slackware 12.0 these device nodes are
automatically created. Did you upgrade from 11.0 to 12.0 and if so,
did you follow the instructions in CHANGES_AND_HINTS.TXT to the
letter? These instructions are critical to the success of your upgrade.

> kobject_add failed for ehci_hcd 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
> =======================
> ieee1394: exports duplicate symbol _csr1212_destroy_keyval (owned by
> kernel)


This and the other -EEXIST and "duplicate symbol" errors are harmless.
They are caused by the fact that you are running a "huge" kernel and
udev is trying to load kernel modules for stuff which is already built
into that huge kernel. If you switch to the "generic" kernel (and
create an initrd for that kernel) these errors will disappear. You
could have found this information in the README.TXT file in the root
of your Slackware 12.0 disk.

Eric
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #3 (permalink)  
Old 02-21-2008, 04:34 AM
Peter
 
Posts: n/a
Default Re: S12 and USB, stock kernel 2.6.21.5-smp #2 SMP

On Wed, 05 Sep 2007 10:38:59 +0200, Eric Hameleers wrote:

snip...
>
> On my fresh install of Slackware 12.0 these device nodes are
> automatically created. Did you upgrade from 11.0 to 12.0 and if so, did
> you follow the instructions in CHANGES_AND_HINTS.TXT to the letter?
> These instructions are critical to the success of your upgrade.


Thank you. This was a clean install.

snip...
>
> This and the other -EEXIST and "duplicate symbol" errors are harmless.
> They are caused by the fact that you are running a "huge" kernel and
> udev is trying to load kernel modules for stuff which is already built
> into that huge kernel. If you switch to the "generic" kernel (and create
> an initrd for that kernel) these errors will disappear. You could have
> found this information in the README.TXT file in the root of your
> Slackware 12.0 disk.
>


I see. I will create a more standard kernel or perhaps even take
the .config from my working S11 configuration and use create my own kernel
again.

Thanks again, Eric.

--
Peter
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #4 (permalink)  
Old 02-21-2008, 04:34 AM
Robby Workman
 
Posts: n/a
Default Re: S12 and USB, stock kernel 2.6.21.5-smp #2 SMP

On 2007-09-04, Peter <peter@localhost.com> wrote:
> In Slackware 12, when inserting a USB stick, the device /dev/sda,b,c,d
> etc, are no longer created as they had been under Slack 11. Therefore,
> using USB sticks, cf cards, etc. is not possible.
>
> My scanner and printer show up with lsusb, but the stick or multi-device
> unit for CF cards do not.
>
> udev and hal are being loaded. I noticed this bug
>
> https://bugs.launchpad.net/ubuntu/+s....20/+bug/88746
>
> In addition, when using my scanner via VMWare (not sane compatible), there
> is a tremendous delay when scanning -- almost like an interrupt conflict
> or problem. This did not occur under S11.
>
> I wanted to know if anyone else has had this or a similar issue. dmesg
> does not show anything obvious other then this sequence of messages:
>
> shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
> Linux agpgart interface v0.102 (c) Dave Jones
> kobject_add failed for uhci_hcd with -EEXIST, don't try to register things
> SNIPPED
> hdc: lost interrupt
>
> (hdc=cdrom)
>
> Anyone else have this issue? Link to additional information?



The "kobject_add failed" messages are the result of udev trying to load
modules for which support is already in the kernel - you are using the
huge{,smp}.s kernel. It is recommended that users use the generic{,smp}.s
kernel instead. I won't go so far as to say that it will have any effect
on your problem, but that would be my first attempt at fixing it.

RW
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #5 (permalink)  
Old 02-21-2008, 04:34 AM
Peter
 
Posts: n/a
Default Re: S12 and USB, stock kernel 2.6.21.5-smp #2 SMP

On Wed, 05 Sep 2007 14:52:03 +0000, Robby Workman wrote:

snip...
>> Anyone else have this issue? Link to additional information?

>
>
> The "kobject_add failed" messages are the result of udev trying to load
> modules for which support is already in the kernel - you are using the
> huge{,smp}.s kernel. It is recommended that users use the
> generic{,smp}.s kernel instead. I won't go so far as to say that it
> will have any effect on your problem, but that would be my first attempt
> at fixing it.
>
> RW


This was my fault. I did not realize I was using HUGE, it just was
installed that way. I upgraded the kernel and used my old working config
and the problems went away.

Thanks all.

--
Peter
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


All times are GMT. The time now is 09:18 AM.


Powered by vBulletin® Version 3.6.5
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.2.0
www.UnixAdminTalk.com