[systemd-devel] Method to solve a "ordering cycle"

[Daniel Spannbauer]

Hello,

I often have a ordering cycle so a service is deleted at boot.

Is there a standard way of getting rid of that cycles or to find the
cause of them?

regards

Daniel
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Persistent virtio device name removal

[Tom Gundersen]

Hi Michael,

A follow-up on this, we finally figured out a way to make virtio
netdev naming persistent [0], so this will work again as of the next
release. It's a shame we had to go back and forth on this, but I hope
it does not cause you too much headaches.

Cheers,

Tom

[0]: 


On Fri, Jul 4, 2014 at 1:31 AM, Tom Gundersen  wrote:
> On Fri, Jul 4, 2014 at 12:55 AM, Michael Marineau
>  wrote:
>> Working on bumping to 215 over here in CoreOS land, but I've got a
>> question regarding the removal of persistent device names for virtio
>> devices since changing the network device names creates a difficult
>> upgrade path from 212. The commit was:
>>
>> http://cgit.freedesktop.org/systemd/systemd/commit/?id=bf81e792f3c0aed54edf004c1c95cc6f6d81d0ee
>> "udev: persistent naming - we cannot use virtio numbers as they are not 
>> stable"
>>
>> The commit doesn't say what the issue was, in what situations are the
>> virtio numbers not stable?
>
> They suffer from the same problem as the ethX enumeration. In many
> cases they appear to be stable (as drivers typically get loaded in the
> same order etc), but there is nothing ensuring it, so we can't rely on
> that.
>
> Cheers,
>
> Tom
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] help : loginctl won't add new seat

[Laércio de Sousa]

Hi Benoit!

I guess you forgot to tag your seat1 card as "master-of-seat".

2015-09-02 6:52 GMT-03:00 Benoit Barthelet :

> long story short I had a working multiseat setup with 2 GPU / 2 mices
> and 2 keyboards
>
> I changed GPU drivers from open-source radeon to fglrx and it stopped
> working
>
> before the driver change I had configured the 2nd seat to used the gpu
> / mice / keys with :
>
> loginctl attach seat1
> /sys/devices/pci:00/:00:01.0/:01:00.0/drm/card0/
> etc..
>
> the issue with the new drivers it seems is that I can't find the card0
> in the /sys hierarchy,
>
> for instance, it seems to be one of my card, but no seat tag :
> udevadm info --query=all
> --path=/sys/devices/pci:00/:00:07.0/:03:00.0
>
> P: /devices/pci:00/:00:07.0/:03:00.0
> E: DEVPATH=/devices/pci:00/:00:07.0/:03:00.0
> E: DRIVER=fglrx_pci
> E: ID_MODEL_FROM_DATABASE=Tahiti PRO [Radeon HD 7950/8950 OEM / R9 280]
> E: ID_PCI_CLASS_FROM_DATABASE=Display controller
> E: ID_PCI_INTERFACE_FROM_DATABASE=VGA controller
> E: ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller
> E: ID_VENDOR_FROM_DATABASE=Advanced Micro Devices, Inc. [AMD/ATI]
> E: MODALIAS=pci:v1002d679Asv174BsdE207bc03sc00i00
> E: PCI_CLASS=3
> E: PCI_ID=1002:679A
> E: PCI_SLOT_NAME=:03:00.0
> E: PCI_SUBSYS_ID=174B:E207
> E: SUBSYSTEM=pci
> E: USEC_INITIALIZED=4263516
>
> So I tried to create manually a udev rule
>
> /etc/udev/rules.d/71-ati.rules
>
> SUBSYSTEM=="pci",
> DEVPATH=="/devices/pci:00/:00:01.0/:01:00.0", TAG+="seat",
> TAG+="master-of-seat"
> SUBSYSTEM=="pci",
> DEVPATH=="/devices/pci:00/:00:07.0/:03:00.0", TAG+="seat",
> TAG+="seat1"
>
> and now loginctl seat-status seat0 gives a master tag after udevadm
> trigger :
> ├─/sys/devices/pci:00/:00:01.0/:01:00.0
>   │ [MASTER] pci::01:00.0
>
> but I can never have a seat1, it never appears so the display manager
> never tries to launch 2nd X session )
>
> I'm at a loss here. any help appreciated
> ___
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>



-- 
*Laércio de Sousa*
*Orientador de Informática*
*Escola Municipal "Professor Eulálio Gruppi"*
*Rua Ismael da Silva Mello, 559, Mogi Moderno*
*Mogi das Cruzes - SPCEP 08717-390*
Telefone: (11) 4726-8313
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] help : loginctl won't add new seat

[Benoit Barthelet]

long story short I had a working multiseat setup with 2 GPU / 2 mices
and 2 keyboards

I changed GPU drivers from open-source radeon to fglrx and it stopped working

before the driver change I had configured the 2nd seat to used the gpu
/ mice / keys with :

loginctl attach seat1
/sys/devices/pci:00/:00:01.0/:01:00.0/drm/card0/
etc..

the issue with the new drivers it seems is that I can't find the card0
in the /sys hierarchy,

for instance, it seems to be one of my card, but no seat tag :
udevadm info --query=all
--path=/sys/devices/pci:00/:00:07.0/:03:00.0

P: /devices/pci:00/:00:07.0/:03:00.0
E: DEVPATH=/devices/pci:00/:00:07.0/:03:00.0
E: DRIVER=fglrx_pci
E: ID_MODEL_FROM_DATABASE=Tahiti PRO [Radeon HD 7950/8950 OEM / R9 280]
E: ID_PCI_CLASS_FROM_DATABASE=Display controller
E: ID_PCI_INTERFACE_FROM_DATABASE=VGA controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=VGA compatible controller
E: ID_VENDOR_FROM_DATABASE=Advanced Micro Devices, Inc. [AMD/ATI]
E: MODALIAS=pci:v1002d679Asv174BsdE207bc03sc00i00
E: PCI_CLASS=3
E: PCI_ID=1002:679A
E: PCI_SLOT_NAME=:03:00.0
E: PCI_SUBSYS_ID=174B:E207
E: SUBSYSTEM=pci
E: USEC_INITIALIZED=4263516

So I tried to create manually a udev rule

/etc/udev/rules.d/71-ati.rules

SUBSYSTEM=="pci",
DEVPATH=="/devices/pci:00/:00:01.0/:01:00.0", TAG+="seat",
TAG+="master-of-seat"
SUBSYSTEM=="pci",
DEVPATH=="/devices/pci:00/:00:07.0/:03:00.0", TAG+="seat",
TAG+="seat1"

and now loginctl seat-status seat0 gives a master tag after udevadm trigger :
├─/sys/devices/pci:00/:00:01.0/:01:00.0
  │ [MASTER] pci::01:00.0

but I can never have a seat1, it never appears so the display manager
never tries to launch 2nd X session )

I'm at a loss here. any help appreciated
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] bootctl: default mount point for the ESP partition.

[Dimitri John Ledkov]

On 1 September 2015 at 17:47, Simon McVittie
 wrote:
> On 01/09/15 17:21, Goffredo Baroncelli wrote:
>> I discovered that bootctl assume as default mount point for the ESP
>> partition the /boot directory. Instead it seems to me that the most part
>> of distributions prefers /boot/efi.
>
> For some context, the reasoning for /boot/efi is:
>
> In principle, it should be possible for the ESP to never be mounted at
> all, copying files in with mtools (or equivalent) when required.
>

In clearlinux we mount ESP at /boot.

However, we disabled the /boot automount, but keep the boot.mount
auto-generated unit.

The reason being, we really don't need /boot in userspace at all,
unless updater is running or one manually wants to mock with things.

What updater does is essentially `systemctl start boot.mount` updates
the kernel images/entries there using files from /usr (sdboot
bootloader, kernel images, initramfs, etc.) And then unmounts /boot.
If one has custom kernels to install one would do the same.

The distinction between "traditional" /boot and /boot/efi is imho
pointless, if one keeps kernel images to be booted on the ESP.

In clearlinux kernel images are EFI apps, packaged with stubs (either
using kernel config, or by means of packing .efi megablob which sdboot
supports to boot everything from).

Doing "traditional" flow of: Firmware -> ESP -> [ grub bootloader ->
find/mount "/boot" ] -> load kernel/initrmafs -> "mount/boot rootfs"
seems more than minimally necessary, when the steps in [] can be
skipped from the bootflow.

-- 
Regards,

Dimitri.
Pura Vida!

https://clearlinux.org
Open Source Technology Center
Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel