The officially official Devuan Forum!

You are not logged in.

#1 Re: Hardware & System Configuration » vdev testing » 2017-01-07 20:32:59

Thanks Ralph,

In poking around trying to cobble together an .act file for the PCTV 290e I found two things:

A)
I managed to break vdev so that the initrd gave an error during boot (I didn't record at the time) boot then continued but something was obviously not setup as before because
the boot finished at a text terminal (rather than GUI login screen).

I think this was caused by my starting to create file /etc/vdev/actions/pctv290e.act(**) with entries certain to be
syntactically incorrect at that time, getting called away, saving the half done file and shutting down.
(**)

-----Content of /etc/vdev/actions/pctv290e.act-----
[vdev-action]
event=any
OS_SUBSYSTEM=dvb
rename_command=

[vdev-action]
event=any
OS_SUBSYSTEM=video4linux
VAR_V4L_OWNER=root
VAR_V4L_GROUP=video
VAR_V4L_MODE=0660
helper=v4l.sh
daemonlet=true

KERNEL=="*demux0", SUBSYSTEM=="dvb", ATTRS{product}=="PCTV 290e", ATTRS{serial}=="00000006LKWJ", SYMLINK+="dvb/adapterPCTV290e/demux0"
KERNEL=="*dvr0", SUBSYSTEM=="dvb", ATTRS{product}=="PCTV 290e", ATTRS{serial}=="00000006LKWJ", SYMLINK+="dvb/adapterPCTV290e/dvr0"
KERNEL=="*frontend0", SUBSYSTEM=="dvb", ATTRS{product}=="PCTV 290e", ATTRS{serial}=="00000006LKWJ", SYMLINK+="dvb/adapterPCTV290e/frontend0"
KERNEL=="*net0", SUBSYSTEM=="dvb", ATTRS{product}=="PCTV 290e", ATTRS{serial}=="00000006LKWJ", SYMLINK+="dvb/adapterPCTV290e/net0"
-----End of Content of /etc/vdev/actions/pctv290e.act-----

On return and reboot the system came up as described. I attempted to fix by login as root, rerun "/usr/share/vdev/vdev-install.sh vdev", reboot.

This made things worse and the boot process froze in the initrd stage and I had to use the power button to shurdown and recover by booting from a refracta
live USB stick, repairing the devuan partition, mounting & chrooting to the devuan partition then running "/usr/share/vdev/vdev-install.sh udev". This booted as normal to the GUI.

I then moved the file /etc/vdev/actions/pctv290e.act outside the vdev structure, ran "/usr/share/vdev/vdev-install.sh vdev" and rebooted. This booted as normal to the GUI

So it *appears* that vdev is not handling malfored rules/actions in a sensible way (or it might be me doing something really stupid!).
Obviously this would require further testing to prove and set out the steps to reproduce and to properly note the errors.
Shall I do this? If I do how/where file a bug report?

B)
I thought it would be helpful to watch what vdev was doing do I tried running vdevd in the foreground:
i) stop the deamon
   /etc/init.d/vdev stop
ii) start vdevd in the foreground
    vdevd -f -v1
This failed with the following error: "28581:00007FA49BEBF700: [          main.c:0053] main: ERROR: vdev_init rc = -22"

Any ideas what I did wrong?

Too hot to think? You need some good old Manchester cold grey drizzle!

#2 Re: Hardware & System Configuration » vdev testing » 2017-01-01 19:37:45

7. Wastebasket (trash icon) works as expected - both the desktop icon & the panel item

#3 Re: Hardware & System Configuration » vdev testing » 2017-01-01 17:52:11

fsmithred wrote:

...
7.  My guess is that gvfs needs some function in udev to tell it something. I run without gvfs here, so I wouldn't have noticed that.
     Does your trash icon work?
8.  You might need to alter some action files or a helper script. The most I've done with that was edit a pattern to find a device and change permissions.

Read Jude's documentation on the action files, (Appendix A)
https://git.devuan.org/unsystemd/vdev/b … to-test.md
https://github.com/jcnelson/vdev/blob/m … to-test.md

Look inside the helper scripts for clues. (in /lib/vdev)

Sorry I can't be more specific. It's a big black box. That I was able to do anything with the action files and permissions.sh was a surprise to me.

7. I don't have the trash icon configured - will give it a try

8. Thanks for the pointer - I'll report back if I can get anywhere (but don't hold your breath!)

#4 Hardware & System Configuration » vdev testing » 2016-12-30 23:12:18

chrisw
Replies: 12

First off, many thanks to Jude Nelson, Ralph Ronnquist and all others who have helped with vdev.
Below is some feedback from my initial try with vdev and request for help (see item 8) to get me a bit further.

Testing vdev on old Dell Inspiron 1525 running devuan beta2, kernel 3.16.0-4-amd64

1) I copied Ralph's packages from https://git.devuan.org/ralph.ronnquist/vdev/tree/master:
libudev1-compat_1.2.1_amd64.deb
libudev1-compat_1.2.1_i386.deb
vdev-initramfs_1.2.7_amd64.deb
vdev-initramfs_1.2.7_i386.deb
vdevd_2.0.2_amd64.deb
vdevd_2.0.2_i386.deb
to a local repository I maintain using aptly (this mostly contains mythtv packages I have compliled for devuan)

2) ensured my local repository was in /etc/apt/sources.lst

3) ran synaptic and "reloaded" (updated) then selected and installed libudev1-compat, vdev-initramfs and vdevd
NOTE: package libudev1-compat would not install properly with error message:
"trying to overwite '/usr/include/libudev.h', which is also in package libudev-dev_215-17+deb8u5"
I therefore uninstalled libudev-dev and retried libudev1-compat which then installed without error

4) As root ran: /usr/share/vdev/vdev-install.sh dialog
and choose vdev then rebooted.

5) All appeared to work as expected (including WiFi)

6) Tried setting PERSISTENT_INTERFACE_NAMEs in /etc/vdev/ifnames.conf
for three network adapters internal WiFi, internal ethernet & external USB ethernet adapter
This apparently had no effect even after reboot until I reran vdev-install.sh and rebooted (this is presumably
expected behaviour? but probably wants documenting)

7) Attaching a USB stick or a USB disk drive did not produce a "mounting" icon on the xfce4 desktop (as would happen with udev on this machine)
although everything was setup okay for manual mounting. Is this expected behavior? Running vdev-install.sh, choosing udev and reboot
and the xfce4 "mounting" icons again worked as expected, reverting to vdev and the xfce4 "mounting" icons failed to work.

8) I attached an external USB HDTV adapter (PCTV 290e) and the expected /dev/dvb devices were created.
However for to test this further on a proper multi-tuner mythtv backend (with the need for consistent and meaningful names),
I would need to be able to recreate the following udev rules in vdev:

# PCTV 290e single tuner USB stick
# --------------------------------
# Create symlinks /dev/dvb/adapterPCTV290e/* pointing to PCTV 290e adapter (has unique attributes, so can find wherever it is)
KERNEL=="*demux0", SUBSYSTEM=="dvb", ATTRS{product}=="PCTV 290e", ATTRS{serial}=="00000006LKWJ", SYMLINK+="dvb/adapterPCTV290e/demux0"
KERNEL=="*dvr0", SUBSYSTEM=="dvb", ATTRS{product}=="PCTV 290e", ATTRS{serial}=="00000006LKWJ", SYMLINK+="dvb/adapterPCTV290e/dvr0"
KERNEL=="*frontend0", SUBSYSTEM=="dvb", ATTRS{product}=="PCTV 290e", ATTRS{serial}=="00000006LKWJ", SYMLINK+="dvb/adapterPCTV290e/frontend0"
KERNEL=="*net0", SUBSYSTEM=="dvb", ATTRS{product}=="PCTV 290e", ATTRS{serial}=="00000006LKWJ", SYMLINK+="dvb/adapterPCTV290e/net0"

I have no idea how to do this! Any help with this would be appreciated.

9) Any other tests you would like doing?

Board footer

Forum Software