Re: [trinity-devel] No USB storage insertion notifications (was: [users] External drive gets mounted twice)
deloptes composed on 2017-02-27 18:47 (UTC+0100):
Felix Miata wrote:
...
I updated Jessie, including bpo 4.9.2, and there's still no notification, plus dmesg is loaded with i915 driver segfaults.
...
What are the kernel versions there. AFAIR it is kernel (usb) -> udev -> dbus. Do you have systemd enabled? I think this information could help not only in your case but also in the case of Thierry.
If I counted right, my previous email reported 10 different installations across 4 64-bit PCs, 9 openSUSE, 1 Jessie. All are inextricably dependent on systemd. The only ones that work right are the 2 oldest openSUSE (42.1), and only with KDE3, which means nothing I've yet tested with a kernel newer than 4.1.36, or with 14.0.x TDE, works. Of the 10, I checked for udisks versions on several, and found both udisks and udisks2 installed on each.
On my debian tde 14.1 with kernel 4.9 all works fine.--
"The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
Felix Miata wrote:
I've yet tested with a kernel newer than 4.1.36, or with 14.0.x TDE, works. Of the 10, I checked for udisks versions on several, and found both udisks and udisks2 installed on each.
dpkg -l | grep udisks ii udisks 1.0.5-1+b1 amd64 storage media interface
This is what I have - Debian is jessie. I hope some of the developers might know the answer to your question. Attached the relevant syslog.
I honestly think this is not exactly TDE problem, you hace errors in your logs from the kernels subsystem. Is it working with other DE on those machines? I would doubt. Is different USB stick working on those machines? I don't have the time now but google "alua: Attach failed (-22)" and similar results with bugs pop up. WTF is alua ? I'll try to find out later.
regards
Am Montag, 27. Februar 2017 schrieb Felix Miata:
If I counted right, my previous email reported 10 different installations across 4 64-bit PCs, 9 openSUSE, 1 Jessie. All are inextricably dependent on systemd. The only ones that work right are the 2 oldest openSUSE (42.1), and only with KDE3, which means nothing I've yet tested with a kernel newer than 4.1.36, or with 14.0.x TDE, works. Of the 10, I checked for udisks versions on several, and found both udisks and udisks2 installed on each.
This will not help you, but I encounted something simillar after reasonly updating my devuan jessie machine. The only hotplugable storage devices left working are usb sticks and CD-ROM/DVDs. All hotplugging functionality for empty CD/DVD is gone, also removable harddisks like RDX drives are not hotpluggable any more. What makes things worse: /proc/sys/kernel/hotplug has gone missing from stock kernel a while ago, so there is no easy way to work around systemd infected software any more (devuan comes systemd-free, but the provided udevd is broken due to systemd)
Nik
Dr. Nikolaus Klepp wrote:
Am Montag, 27. Februar 2017 schrieb Felix Miata:
If I counted right, my previous email reported 10 different installations across 4 64-bit PCs, 9 openSUSE, 1 Jessie. All are inextricably dependent on systemd. The only ones that work right are the 2 oldest openSUSE (42.1), and only with KDE3, which means nothing I've yet tested with a kernel newer than 4.1.36, or with 14.0.x TDE, works. Of the 10, I checked for udisks versions on several, and found both udisks and udisks2 installed on each.
This will not help you, but I encounted something simillar after reasonly updating my devuan jessie machine. The only hotplugable storage devices left working are usb sticks and CD-ROM/DVDs. All hotplugging functionality for empty CD/DVD is gone, also removable harddisks like RDX drives are not hotpluggable any more. What makes things worse: /proc/sys/kernel/hotplug has gone missing from stock kernel a while ago, so there is no easy way to work around systemd infected software any more (devuan comes systemd-free, but the provided udevd is broken due to systemd)
Nik
I've never used such exotic like RDX and regarding CD-ROM/DVD I am not sure if I understand correctly. Do you mean when you insert an empty CD/DVD disk the system does not respond? What is the expected behavior? I recently removed the CD/DVD drive and replaced it with hdd bay where I put a second ssd
regards
Am Mittwoch, 1. März 2017 schrieb deloptes:
I've never used such exotic like RDX and regarding CD-ROM/DVD I am not sure if I understand correctly. Do you mean when you insert an empty CD/DVD disk the system does not respond? What is the expected behavior? I recently removed the CD/DVD drive and replaced it with hdd bay where I put a second ssd
Hi!
Yes, insering an empty CD/DVD used to trigger an udev event, which started k3b in the end. RDX is basicly a usb-sdd, where the actual storage device triggerd a "capacity change" event, when inserting a disk.
Both things are not happening any more since the last update. But that's not a TDE issue, it's a systemd-broke-another-thing-issue - hopefully vdev will be there, soon.
Nik
Dr. Nikolaus Klepp wrote:
Yes, insering an empty CD/DVD used to trigger an udev event, which started k3b in the end. RDX is basicly a usb-sdd, where the actual storage device triggerd a "capacity change" event, when inserting a disk.
Both things are not happening any more since the last update. But that's not a TDE issue, it's a systemd-broke-another-thing-issue - hopefully vdev will be there, soon.
it might be TDE problem, because I do not understand how systemd would know which is your cd burning app
Last update of what?
regards
Am Mittwoch, 1. März 2017 schrieb deloptes:
it might be TDE problem, because I do not understand how systemd would know which is your cd burning app
Last update of what?
when "udevadm monitor" gives no output and the kernel log gives no line when insering an empty CD/DVD, then it's most unlikely to be a TDE problem.
nik
-
deloptes -
Dr. Nikolaus Klepp -
Felix Miata