Arch Linux

ilmorris

Member

Registered: 2005-07-28

Posts: 55

Hotplug Errors During Startup

Hello,

  I decided to give Archlinux a try at the suggestion of a friend this evening.  The install went very smooth, although I am getting errors with hotplug everytime my system boots.

/var/log/errors.log shows the following:

Jul 27 21:58:47 tux_1 shpchp: shpc_init : shpc_cap_offset == 0
Jul 27 21:58:47 tux_1 shpchp: shpc_init : shpc_cap_offset == 0
Jul 27 21:58:49 tux_1 CS4232 soundcard not found or device busy
Jul 27 21:58:50 tux_1 CS4232 soundcard not found or device busy
Jul 27 21:58:50 tux_1 No WaveFront cards found or devices busy
Jul 27 21:58:50 tux_1 No WaveFront cards found or devices busy

I have an nforce chipset and have been using the intel8x0 module for sound on other linux distro's.

I searched the forums and found another post regarding these same errors and did as it suggested and placed the items into the hotplug blacklist.  However, it appears that file is being ignored by my system as I still recieve the errors when Hotplug starts at boot.  Can anyone give me a suggestion as to what I can do to resolve the issue?  Thanks.

scarecrow

Member

From: Greece

Registered: 2004-11-18

Posts: 715

Re: Hotplug Errors During Startup

Most Archlinux users have disabled hotplug and use "lshwd" instead.

---

Microshaft delenda est

jackmetal

Member

From: US

Registered: 2005-06-13

Posts: 164

Re: Hotplug Errors During Startup

Most Archlinux users have disabled hotplug and use "lshwd" instead.

I'm honestly Not trying to hijack the thread, but was just curious.  I don't use lshwd or hotplug, I manually set the modules I want loaded..But.....How would you use lshwd instead of hotplug?

---

--

Some of the world's greatest feats were
accomplished by people not smart enough
to know they were impossible.
-- Doug Larson

iphitus

Forum Fellow

From: Melbourne, Australia

Registered: 2004-10-09

Posts: 4,927

Re: Hotplug Errors During Startup

Many arch users dont use either, I for one dont, as I dont see the point of having it detect my modules on boot, every boot when I know for a fact that they arent going to be changing dramatically anytime soon.

i also use the MODULES line.

iphitus

ilmorris

Member

Registered: 2005-07-28

Posts: 55

Re: Hotplug Errors During Startup

Would not using hotplug affect anything if I am also using UDEV?  My previous linux distro requested that both be installed for 'proper' UDEV functionality.

phrakture

Arch Overlord

From: behind you

Registered: 2003-10-29

Posts: 7,879

Website

Re: Hotplug Errors During Startup

Would not using hotplug affect anything if I am also using UDEV?  My previous linux distro requested that both be installed for 'proper' UDEV functionality.

Man, I'm going to write a blog post about this and continually link to it - I say it often enough:

Hotplug, as an rc.d script, is *not* the same thing as what udev uses.
Hotplug is primarilly a set of scripts that takes a device and finds what modules are needed for it.  udev calls these scripts just fine.

The rc.d script run at boot actually performs what is known as "cold plugging" - that is, it detects modules for all the devices *already plugged in* to the system.

I can tell you with absolute certainty that removing hotplug will not harm anything at all - I have 5 arch boxes and have never-ever-ever used the hotplug boot daemon.

---

http://phraktured.net

lanrat

Member

From: Poland

Registered: 2003-10-28

Posts: 1,274

Re: Hotplug Errors During Startup

What's more:

/etc/dev.d/ + /etc/hotplug.d/ directory multiplexing is completely
  removed from udev itself and must be emulated by calling small
  helper binaries provided in the extras folder:
    make EXTRAS=extras/run_directory/
  will build udev_run_devd and udev_run_hotplugd, which can be called
  from a rule if needed:
    RUN+="/sbin/udev_run_hotplugd"
  The recommended way to handle this is to convert all the calls from
  the directories to explicit udev rules and get completely rid of the
  multiplexing. (To catch a ttyUSB event, you now no longer need to
  fork and exit 300 tty script instances you are not interested in, it
  is just one rule that matches exactly the device.)

Default arch udev rules support calling hotplug scripts of course so there shouldn't be any problems.
You can also convert them into pure udev rules like I did for my cam for example:
http://bbs.archlinux.org/viewtopic.php?t=13870

The problem is you would need more than 250 rules for all cams supported by libgphoto2 :-) (all vendor and product id pairs)
Some usb devices don't return enough info to write one or a few generalized rules.

Gullible Jones

Member

Registered: 2004-12-29

Posts: 4,863

Re: Hotplug Errors During Startup

Jul 27 21:58:47 tux_1 shpchp: shpc_init : shpc_cap_offset == 0
Jul 27 21:58:47 tux_1 shpchp: shpc_init : shpc_cap_offset == 0

Dunno what that's about... I have shpchp run at startup and it doesn't give me any messages like that.

Jul 27 21:58:49 tux_1 CS4232 soundcard not found or device busy
Jul 27 21:58:50 tux_1 CS4232 soundcard not found or device busy
Jul 27 21:58:50 tux_1 No WaveFront cards found or devices busy
Jul 27 21:58:50 tux_1 No WaveFront cards found or devices busy

That's a known problem... If you don't blacklist those modules, Hotplug will complain.

The error messages you posted are in all likelihood completely harmless. Still, Hotplug is known to be slow, finicky, and whiny, and always has been in my experience; unless you have a good reason to use it, it is probably better to load your modules via rc.conf.

ilmorris

Member

Registered: 2005-07-28

Posts: 55

Re: Hotplug Errors During Startup

Thanks for the suggestions everyone.  I think I am going to do as suggested here and just remove hotplug from startup and load modules manually in rc.conf.  Thanks again.