Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 61329 - hotplug bug with input device
Summary: hotplug bug with input device
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All All
: High normal (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-23 00:45 UTC by Patrizio Bassi
Modified: 2004-10-01 09:47 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Patrizio Bassi 2004-08-23 00:45:47 UTC
i've a Logitech ThunderPad Digital joystick connectect via the gameport of my audio card.
no problem with it, it works, but that's a little problem with hotplug:

when it starts is gives errors on
/etc/hotplug/input.rc, line 85

84: P:* )       # Physical
85:                eval "${line#P: }"
86:                PHYS=$Phys

when it have to find the phisical port the joystick is connected to.
infact i have in my dmesg:

input: ImPS/2 Generic Wheel Mouse on isa0060/serio1
input: AT Translated Set 2 keyboard on isa0060/serio0
...
input: Logitech ThunderPad Digital [ThunderPad] on <NULL>
...

so it can't find the port.
Comment 1 Greg Kroah-Hartman (RETIRED) gentoo-dev 2004-09-20 16:18:06 UTC
Thanks, is now fixed upstream and will show up in the next release (today or tommorrow).
Comment 2 Patrizio Bassi 2004-09-22 00:19:59 UTC
i compiled new version.

NOT FIXED!!!
i get the SAME error plus another one:

isapnp.rc line 16 and a message complaining about "return" statement.

it was better before :)

in dmesg i always have
input: Logitech ThunderPad Digital [ThunderPad] on <NULL>

so...not fixed. please reopen
Comment 3 Dietrich Heise 2004-09-22 02:22:44 UTC
same error for me,
usb mouse not usable!
And also the modules for the network card does not load by hotplug :(
Comment 4 Dietrich Heise 2004-09-22 05:46:49 UTC
ok,

there is a typo in the hotplug-20040920.ebuild

[...]
    ewarn "WARNING: did, then emerge the coolplug package."
[...]

the package is named "coldplug" not "coolplug"
But I wonder why not add "coldplug" as DEPEND?
Comment 5 Greg Kroah-Hartman (RETIRED) gentoo-dev 2004-09-23 11:30:01 UTC
I'll go fix the typo, thanks.

And it's not marked as a DEPEND, as 90% of the users do not need coldplug support.
Comment 6 Robert Moss (RETIRED) gentoo-dev 2004-09-23 13:14:47 UTC
Well 90% is neither everyone nor noone, so surely that should be a local USE flag?
Comment 7 Greg Kroah-Hartman (RETIRED) gentoo-dev 2004-09-23 16:42:31 UTC
Huh?  a USE flag to install a separate package?  And then install it using rc-update?  How?
Comment 8 Robert Moss (RETIRED) gentoo-dev 2004-09-24 09:49:58 UTC
MY_DEPEND="${DEPEND}
    coldplug? ( sys-apps/coldplug )"

My DEPEND would, methinks, be more correct than yours, as this package *can* make use of coldplug. Well, it would be... *if* I'd got my facts right. Actually it would appear that coldplug is nothing to do with hotplug, it's a drop-in replacement, so ignore me :-P
Comment 9 Greg Kroah-Hartman (RETIRED) gentoo-dev 2004-10-01 09:47:37 UTC
No, the coldplug package requires the hotplug package, not the other way around.

If you want the functionality of loading modules at boot time, for devices
that have been found before init happens, then use coldplug.

Making hotplug install coldplug is the wrong thing to do, as hotplug does not
require the coldplug stuff at all to work properly.