Re: [oi-dev] OI no longer automounts USB sticks

2021-06-06 Thread Andreas Wacknitz



On 6/6/21 9:43 PM, Gary Mills wrote:

On Sun, Jun 06, 2021 at 11:06:06AM -0700, Alan Coopersmith wrote:

hal monitors the devices and uses dbus to send messages to other programs
on certain events - like notifying the GNOME/Mate file manager when a new
removable media device is inserted or removed so they can show/hide it.

So, I got it backwards.  dbus is only a message bus or a rendevous
point.  It's hal that's likely responsible for ignoring changes to
USB devices.  I've already got ideas how to debug this problem.



service/hal is delivered by illumos-gate

___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev


Re: [oi-dev] OI no longer automounts USB sticks

2021-06-06 Thread Gary Mills
On Sun, Jun 06, 2021 at 11:06:06AM -0700, Alan Coopersmith wrote:
> 
> hal monitors the devices and uses dbus to send messages to other programs
> on certain events - like notifying the GNOME/Mate file manager when a new
> removable media device is inserted or removed so they can show/hide it.

So, I got it backwards.  dbus is only a message bus or a rendevous
point.  It's hal that's likely responsible for ignoring changes to
USB devices.  I've already got ideas how to debug this problem.


-- 
-Gary Mills--refurb--Winnipeg, Manitoba, Canada-

___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev


Re: [oi-dev] OI no longer automounts USB sticks

2021-06-06 Thread Gary Mills
On Fri, Jun 04, 2021 at 03:11:32PM -0500, Gary Mills wrote:
> 
> Ah, I tried the first command on an OI system running the 2020-11-27
> BE and did get some output while I inserted and removed a USB stick:
> 
> # lshal --monitor
> 
> Start monitoring devicelist:
> -
> pci_0_0/pci1022_1453_1_3/pci1b21_1142_0/storage_a_0 added
> pci_0_0/pci1022_1453_1_3/pci1b21_1142_0/storage_a_if0_0 added
> pci_0_0/pci1022_1453_1_3/pci1b21_1142_0/storage_a_if0_0/scsi_host0 added
> pci_0_0/pci1022_1453_1_3/pci1b21_1142_0/storage_a_if0_0/scsi_host0/disk4 
> added
> 
> pci_0_0/pci1022_1453_1_3/pci1b21_1142_0/storage_a_if0_0/scsi_host0/disk4/sd4 
> added
> 
> pci_0_0/pci1022_1453_1_3/pci1b21_1142_0/storage_a_if0_0/scsi_host0/disk4/sd4/p0_1
>  added
> 
> pci_0_0/pci1022_1453_1_3/pci1b21_1142_0/storage_a_if0_0/scsi_host0/disk4/sd4/p0_1
>  property volume.mount_point = '/media/STORE N GO'
> 
> pci_0_0/pci1022_1453_1_3/pci1b21_1142_0/storage_a_if0_0/scsi_host0/disk4/sd4/p0_1
>  property volume.is_mounted_read_only = false (new)
> 
> pci_0_0/pci1022_1453_1_3/pci1b21_1142_0/storage_a_if0_0/scsi_host0/disk4/sd4/p0_1
>  property volume.is_mounted = true
> 
> pci_0_0/pci1022_1453_1_3/pci1b21_1142_0/storage_a_if0_0/scsi_host0/disk4/sd4/p0_1
>  property volume.mount_point = ''
> 
> pci_0_0/pci1022_1453_1_3/pci1b21_1142_0/storage_a_if0_0/scsi_host0/disk4/sd4/p0_1
>  property volume.is_mounted = false
> 
> pci_0_0/pci1022_1453_1_3/pci1b21_1142_0/storage_a_if0_0/scsi_host0/disk4/sd4/p0_1
>  removed
> 
> pci_0_0/pci1022_1453_1_3/pci1b21_1142_0/storage_a_if0_0/scsi_host0/disk4/sd4 
> removed
> pci_0_0/pci1022_1453_1_3/pci1b21_1142_0/storage_a_if0_0/scsi_host0/disk4 
> removed
> pci_0_0/pci1022_1453_1_3/pci1b21_1142_0/storage_a_if0_0/scsi_host0 removed
> pci_0_0/pci1022_1453_1_3/pci1b21_1142_0/storage_a_if0_0 removed
> pci_0_0/pci1022_1453_1_3/pci1b21_1142_0/storage_a_0 removed
> 

I also tried "dbus-monitor --system" on the same system as I inserted
and removed a USB stick.  I got too much output to capture, but this
is part of it:

method call time=1622910378.194372 sender=:1.39 ->
destination=org.freedesktop.Hal serial=555

path=/org/freedesktop/Hal/devices/pci_0_0/pci1022_1453_1_3/pci1b21_1142_0/storage_a_if0_0/scsi_host0/disk4/sd4/p0_1;
interface=org.freedesktop.Hal.Device; member=GetAllProperties
method return time=1622910378.194409 sender=:1.2 -> destination=:1.39 
serial=867 reply_serial=555
   array [
...
  dict entry(
 string "org.freedesktop.Hal.Device.Volume.method_execpaths"
 variant array [
   string "hal-storage-mount"
   string "hal-storage-unmount"
   string "hal-storage-eject"
]
  )
...
  dict entry(
 string "volume.label"
 variant string "STORE N GO"
  )
...
  dict entry(
 string "block.solaris.raw_device"
 variant string "/dev/rdsk/c4t0d0p0:1"
  )
  dict entry(
 string "block.device"
 variant string "/dev/dsk/c4t0d0p0:1"
  )
...

Note that the "lshal" output shows the mount point as '/media/STORE N
GO', but the "dbus" output only shows the device name.  "/media" is
the mount point used by the "rmvolmgr" daemon and the "rmmount"
command.  Something must have mounted the USB stick between those two
services.  I'm not familiar with this area of OI; I only know what I
saw in the output cited above.  However, something must have convinced
"dbus" to send those messages when the USB stick was inserted.  I don't
know what is missing or changed in the current OI BE so that it seems
to ignore USB devices.


-- 
-Gary Mills--refurb--Winnipeg, Manitoba, Canada-

___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev


Re: [oi-dev] OI no longer automounts USB sticks

2021-06-06 Thread Alan Coopersmith

On 6/6/21 10:30 AM, Gary Mills wrote:

As far as I can tell, "dbus" sends messages to "hal" about the state
of devices on the system.  However, for insertion of USB sticks, this
does not happen.  I don't know why it doesn't happen.


hal monitors the devices and uses dbus to send messages to other programs
on certain events - like notifying the GNOME/Mate file manager when a new
removable media device is inserted or removed so they can show/hide it.

-alan-

___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev


Re: [oi-dev] OI no longer automounts USB sticks

2021-06-06 Thread Gary Mills
On Fri, Jun 04, 2021 at 01:16:38PM -0500, Gary Mills wrote:
> I tried both of those commands, and got no output.

That was "lshal --monitor" and "dbus-monitor --system" on a recent BE.
Both of those commands produced no output.  I know they work because I
tried both of them on another system that was booted back to an older
BE.  There, both of them produced copious output, just as the support
document showed.

> The insertion and
> removal does appear in /var/adm/messages, but goes no further.

Here's what I saw on insertion of a USB stick:

Jun  5 16:52:03 z400 usba: [ID 912658 kern.info] USB 2.0 device 
(usb951,160b) operating at hi speed (USB 2.x) on USB 2.0 root hub: storage@6, 
scsa2usb3 at bus address 3
Jun  5 16:52:03 z400 usba: [ID 349649 kern.info] Kingston DataTraveler2.0  
0805050224383
Jun  5 16:52:03 z400 genunix: [ID 936769 kern.info] scsa2usb3 is 
/pci@0,0/pci103c,1309@1a,7/storage@6
Jun  5 16:52:03 z400 genunix: [ID 408114 kern.info] 
/pci@0,0/pci103c,1309@1a,7/storage@6 (scsa2usb3) online
Jun  5 16:52:03 z400 scsi: [ID 583861 kern.info] sd9 at scsa2usb3: target 0 
lun 0
Jun  5 16:52:03 z400 genunix: [ID 936769 kern.info] sd9 is 
/pci@0,0/pci103c,1309@1a,7/storage@6/disk@0,0
Jun  5 16:52:03 z400 genunix: [ID 408114 kern.info] 
/pci@0,0/pci103c,1309@1a,7/storage@6/disk@0,0 (sd9) online
Jun  5 16:52:03 z400 genunix: [ID 127566 kern.info] device 
pciclass,03@0(display#0) keeps up device sd@0,0(disk#9), but the former is 
not power managed

Note that the messages show only "sd9" as the disk device name.  This
is the old-style name, one that is no longer used.  /dev/sd9 does not
exist.  The "rmformat" command show the device name as:
/dev/rdsk/c8t0d0p0 .  It does exist, as does the block device:
/dev/dsk/c8t0d0p0 .

As far as I can tell, "dbus" sends messages to "hal" about the state
of devices on the system.  However, for insertion of USB sticks, this
does not happen.  I don't know why it doesn't happen.


-- 
-Gary Mills--refurb--Winnipeg, Manitoba, Canada-

___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev