You are not logged in.
While browsing my journal, I noticed a few errors on some udev rules that I had written and which used to work perfectly fine.
Like this:
Failed to write ATTR{/sys/devices/pci0000:00/0000:00:14.0/usb3/3-10/3-10.2/3-10.2:1.3/power/wakeup}="enabled"ls'ing the path showed that it's now valid up to the 'power' node, but there isn't any 'wakeup' sub-node anymore. Is this a known change and does anyone know how to deal with such rules now?
Thanks!
Note: an example of such rule that I use:
ACTION=="add|change", SUBSYSTEM=="usb", DRIVERS=="usb", ATTRS{idVendor}=="1e7d", ATTRS{idProduct}=="2de6", ATTR{power/wakeup}="enabled"Last edited by OpusOne (2024-07-24 21:49:14)
Offline
Skip wakeup ? Or see and figure out (eventually post) from command: 'tree -hif /sys/devices/pci0000\:00/|less' .
Offline
Is it working with a kernel out of the 6.9 series or the LTS one?
Offline
I haven't had time to downgrade and see at which point exactly the 'wakeup' node stopped being created, at least for USB devices. Could have been earlier than kernel 6.10 - I noticed it while browsing the journal, but I may have missed it in 6.9.
Whatever it is, there's clearly a change. The wakeup node was absolutely present until relatively recently. And this is the recommended way of doing it via udev: https://wiki.archlinux.org/title/Power_ … p_triggers
In my case, I have two udev rules, one to enable wakeup for a specific USB device that didn't have it enabled by default, and conversely, another rule to disable wakeup for a device that had it enabled by default. It was working 100% fine.
Interestingly, the device that didn't have wakeup enabled by default does now wakeup the system, in spite of the rule not working anymore. Definitely there has been a change somewhere for this wakeup property. If anyone can find what it is and when...
Offline
Looking at current sysfs on my machine with kernel 6.10, I noticed that the 'wakeup' node was now in the following path for the same device:
/sys/devices/pci0000:00/0000:00:14.0/usb3/power/wakeup
instead of:
/sys/devices/pci0000:00/0000:00:14.0/usb3/3-10/3-10.2/3-10.2:1.3/power/wakeup
But the latter is the path we get from udev. So, there's definitely something that has changed, and may either need an update to udev, or may require a change in udev rules. Or maybe the change in sysfs was unintentional.
Also, not ultra-familiar with sysfs. I suspect the former path is for the USB hub rather than the device itself. Am I right?
Last edited by OpusOne (2024-07-25 21:35:59)
Offline