Modify

Opened 3 years ago

Last modified 3 years ago

#18116 new defect

At boot /etc/hotplug scripts are not triggered by kernel events

Reported by: spon901@… Owned by: developers
Priority: normal Milestone: Barrier Breaker 14.07
Component: base system Version: Barrier Breaker 14.07
Keywords: Cc:

Description

At boot /etc/hotplug.d scripts are not triggered by kernel events.
If we have a HDD atached to an usb port, at boot, those scripts are not executed. However when we add/remove it later, after boot those scripts are executed properly. This was not happened before introducing procd, and there is no way to make this happened through settings.

Attachments (0)

Change History (6)

comment:1 Changed 3 years ago by anonymous

which script specifically does not get called ?

comment:2 Changed 3 years ago by anonymous

Possibly the same problem as /ticket/18103.html ? Some hotplug activities not taking place initially, manually triggering them being the only way...

comment:3 Changed 3 years ago by spon901@…

The scripts from /etc/hotplug.d ar enot called when the router power up, even if seems to have kernelk events.. It the router power up having a HDD attached there is a kernel event that see that HDD but /etc/hotplug.d/block scriptsa are not executed. If unplug and plug that HDD after the router is up, same kernel event occur, but this time /etc/hotplug.d/block scripts are executed as expected. Prior introducing procd, the scripts are executed in both cases.

It might be related to 18103

comment:4 Changed 3 years ago by Grrruk

The same the problem here: I have serial-over-usb modem, so I placed a script in /etc/hotplug.d/tty to run agetty on /dev/ttyUSB0. It works if I plug and unplug modem while router power on, but nothing happens if I power cycle router (Asus RT-N18U, CC). It just does not initialize.

If it's designed this way and not a bug, please, please say so in hotplug section of wiki.

comment:5 Changed 3 years ago by anonymous

Same here with usb printers. Running CC trunk r45802

comment:6 Changed 3 years ago by anonymous

Should add to the above report that the printer issue is on a Tplink Archer C7 v2.

Have added the following into rc.local to fix

# Wait till everything has properly started up
sleep 10

# Hotplug doesn't pick up the usb printers on boot - a reset of the bus triggers the hotplug add event
echo "1" > /sys/bus/usb/devices/usb1/bConfigurationValue
echo "1" > /sys/bus/usb/devices/usb2/bConfigurationValue

Add Comment

Modify Ticket

Action
as new .
Author


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

 
Note: See TracTickets for help on using tickets.