roseSUBSYSTEM=="media", GROUP="video" line to SUBSYSTEM=="media", GROUP="video", MODE="0666" if you dont want to add your user to the video groupCC: @[email protected]
in 50-udev-default.rules, you can also change the
CC: @[email protected]
CC: @[email protected]
Big Shallot 
@rose but how is it working with only
SUBSYSTEM=="media", GROUP="video" with eudev, is this an internal eudev thing ?@rose wait lol, i never did read the logs with with eudev, wireplumber has the same complaints but still starts
@rose oh, actully it starts but i only have the dummy device
okay okay, as root run
gardendevctl trigger
mdevd-coldplug
gardendevctl trigger
and then check again
gardendevctl trigger
mdevd-coldplug
gardendevctl trigger
and then check again
@rose still only a dummy device
And another tengential issue, dhcpcd can't find the interfaces at boot but find them fine it restarted later
And another tengential issue, dhcpcd can't find the interfaces at boot but find them fine it restarted later
@[email protected] I pushed a fix to gardendevd and libudev-zero, haven't had the chance to test it though, if you want to you can try it
@rose neat, lets get testing 
@rose wait i did not package ur libudev-zero i was using the distro one, maybe i should do that 
@rose im packaging 
@rose its working 
!!! also im onto something for my network interfaces not being detected at boot, i need to investigate more
The only other thing is your mdevd service complaining about logging to /var/log at sysinit, before localmount get run and mount my var partition :/
!!! also im onto something for my network interfaces not being detected at boot, i need to investigate moreThe only other thing is your mdevd service complaining about logging to /var/log at sysinit, before localmount get run and mount my var partition :/
@rose and login to a wayland session fails for the first time after boot, successive attempts are working tho 
@rose yes i am
@rose im using river, ill send u logs once i reboot
@rose dang its a greetd issue, launching from tty works flawlessly
are you able to modify the commands that greetd runs and have it also run
CC: @[email protected]
ls -alh /dev/dri and ssave it to the logCC: @[email protected]
@rose wtf having greetd launch `sh -c 'ls -lah /dev/dri > ~/dri.log ; river'` makes river starts without issue 
do you launch greetd through openrc? try adding
after mdevd-init gardendev-trigger to the service file depends@rose it doesnt changes a thing :/
hm alright
its just a standard alpine setup with greetd and river, right? i'll set up a vm to test that later
its just a standard alpine setup with greetd and river, right? i'll set up a vm to test that later
@rose it is, though u'll have to write a river.desktop wayland-session manually as the package doesnt have one :/
@rose yeah same issue with labwc, ive just tested
@rose i wrote APKBUILDS for gardendevd and libudev-zero-gardenhouse if thats usefull :
https://codeberg.org/Topoetry/wip-aports
https://codeberg.org/Topoetry/wip-aports
okay i cant replicate it
are you using greetd with tuigreet or something else? it all kinda just works for me
gardendevd, gardendev-trigger, gardendev-settle and mdevd in sysinit, mdevd-init, dhcpcd and greetd in default
CC: @[email protected]
are you using greetd with tuigreet or something else? it all kinda just works for me
gardendevd, gardendev-trigger, gardendev-settle and mdevd in sysinit, mdevd-init, dhcpcd and greetd in default
CC: @[email protected]
@rose im using tuigreet, and no dhcpcd service, it just get called by the default networking service in boot
@rose weeeh, what could be the issue then :/
honestly no idea, dhcpcd not seeing the network devices makes me think that there still is an older version of libudev-zero being used
@rose but your libudev-zero is the only one installed on my system :/
@[email protected] yeah that's the weird part
it could also be some timing thing, but the latest commit in both repos should've fixed it
it could also be some timing thing, but the latest commit in both repos should've fixed it
@rose i keep combing through my logs and looking at my configs deviating from the packages default configs and nothing useful :'c
@[email protected] could you just like
send me a list of the groups your user is in, the services that are enabled (just run rc-update) and all packages you have installed? I'll try to get a setup as close to yours as possible tomorrow
send me a list of the groups your user is in, the services that are enabled (just run rc-update) and all packages you have installed? I'll try to get a setup as close to yours as possible tomorrow
@rose i can even send u a lbu tarball sanitized from my user info
@[email protected] thanks I'll try it tomorrow
uhmm looking at your world file, you have libudev-zero-gardenhouse-helper, but not libudev-zero-gardenhouse listed, the helper thingy shouldn't be required (i should probably remove it from the repo), maybe try installing the non helper package?
@rose oh yeah i was testing with it, the non-helper package is definitely installed, i defined it as a gardendev hard dependency
okay i figured out the issue
eudev ships older udev rules, for example /dev/dri/renderD* is added to the
your gardendevd package may have to ship its own set of default rules taken from eudev https://github.com/eudev-project/eudev/tree/master/rules
eudev ships older udev rules, for example /dev/dri/renderD* is added to the
render group instead of the video groupyour gardendevd package may have to ship its own set of default rules taken from eudev https://github.com/eudev-project/eudev/tree/master/rules
@rose the eudev master branch is fuggedup, the release (the one actually shipped by alpine) do add renderD* to the video group, but i'll look at that a bit later, maybe there's something else
https://github.com/eudev-project/eudev/blob/v3.2.14/rules/50-udev-default.rules
https://github.com/eudev-project/eudev/blob/v3.2.14/rules/50-udev-default.rules
yeah, they add renderD* to the video group, when gardendevd and new systemd-udevd add it to the render group, which doesn't exist on alpine, that's the issue
@rose ooooh right, ill definitely be patching those rule a bit later then :3
@rose weeh, even with the eudev rules my issue of video and network devices only working after the second time they are accessed persists 
this is so weird
can you try adding your user to the
that may at least fix the video thing, i have no idea why network doesn't work tho honestly
CC: @[email protected]
can you try adding your user to the
video groupthat may at least fix the video thing, i have no idea why network doesn't work tho honestly
CC: @[email protected]
@rose i can also just login twice for the video issue or prefix all compositor commands with
ls /dev/dri;