On Tue, Jan 23, 2018 at 2:08 AM, Michael wrote:
> Hi
> why can't the Udev rules be automated or removed? As described here users
> only need to paste infos from lsusb etc.
> https://forums.x-plane.org/index.php?/forums/topic/72733-writing-and-debugging-udev-rules/&page=2
> But such a huge pain in
On Tue, Sep 12, 2017 at 01:38:00PM +0200, Lennart Poettering wrote:
> On Mo, 11.09.17 11:47, Dmitry Torokhov (dmitry.torok...@gmail.com) wrote:
>
> > Previously we were loading kernel modules on all device events save
> > for "remove". With the introduction of KOBJ_
Previously we were loading kernel modules on all device events save
for "remove". With the introduction of KOBJ_BIND/KOBJ_UNBIND this causes
issues, as driver modules that have devices bound to their drivers get
immediately reloaded, and it appears to the user that module unloading
does not work.
Newer kernels will emit uevents with "bind" and "unbind" actions. These
uevents will be issued when driver is bound to or unbound from a device.
"Bind" events are helpful when device requires a firmware to operate
properly, and driver is unable to create a child device before firmware
is properly l
On Wednesday, December 19, 2012 03:52:08 PM Lennart Poettering wrote:
> On Fri, 14.12.12 06:04, Reindl Harald (h.rei...@thelounge.net) wrote:
> > WARNING: at fs/ext4/super.c:339 ext4_journal_start_sb+0x11e/0x130()
> > Hardware name: VMware Virtual Platform
> > Modules linked in: binfmt_misc cls_u32
