Opened 11 years ago

Closed 10 years ago

#2117 closed defect (wontfix)

missing udevtrigger

Reported by: jake1981@… Owned by: developers
Priority: high Milestone:
Component: packages Version:
Keywords: udevtrigger Cc:


If you build kamikaze from development branch, after install syslog informs of missing file: hotplug2.
So you can install it as a ipkg or you can have it included in your build also..
But after installing hotplug2, syslog informs another missing file: udevtrigger

It's possible to build udevtrigger as included to image or as ipkg, but buildroot's menu doesn't have it. To be able to build it you need to add "CONFIG_PACKAGE_udev=[m/y]" and "CONFIG_PACKAGE_udevtrigger=[m/y]" to .config in your buildroot directory manually.

udevtrigger should be added as a menu option for buildroot. Set your syslogd to start early(01) and change it's initscript to create /var/log before startup of syslogd to re-produce this error. Also, edit boot initscript, remove syslogd and klogd startup from there.. (as they already are started at 01) to re-produce.

Attachments (0)

Change History (5)

comment:1 follow-up: Changed 11 years ago by loswillios

Utilities -> hotplug2
Utilities -> udevtrigger

comment:2 in reply to: ↑ 1 Changed 11 years ago by anonymous

Replying to loswillios:

Utilities -> hotplug2
Utilities -> udevtrigger

Issue is still open. According to package's Makefile, udev is dependant on 2.6 kernel. This issue happens with brcm-2.4

comment:3 Changed 11 years ago by florian

  • Resolution set to worksforme
  • Status changed from new to closed

Yes, udev cannot be used with a 2.4 kernel, but hotplug2 can. hotplug2 can report that udevtrigger cannot be found, but this is no problem.

comment:4 Changed 10 years ago by anonymous

  • Resolution worksforme deleted
  • Status changed from closed to reopened

udevtrigger is required for hotplug2 --coldplug to work, so hotplug2 lacks some serious funcionality without udevtrigger :/

comment:5 Changed 10 years ago by florian

  • Resolution set to wontfix
  • Status changed from reopened to closed

According to the documentation of hotplug2 :

Binary 'udevtrigger' from udev is necessary on 2.6 for initial devices detection, however, using --no-udevtrigger parameter, it can be switched off. Application 'hotplug2-coldplug-2.4' is provided for initial devices detection on 2.4 kernels.}}}

I do not loose anything without udevtrigger. Please do not debate or re-open this ticket.

Add Comment

Modify Ticket

as closed .
The resolution will be deleted. Next status will be 'reopened'.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.