| 1 |
On Sunday, 17 April 2022 20:17:47 -00 Rich Freeman wrote: |
| 2 |
> On Sun, Apr 17, 2022 at 1:05 PM Martin Vaeth <martin@×××××.de> wrote: |
| 3 |
> > Peter Humphrey <peter@××××××××××××.uk> wrote: |
| 4 |
> > > On Sunday, 17 April 2022 16:42:35 -00 Martin Vaeth wrote: |
| 5 |
> > >> Peter Humphrey <peter@××××××××××××.uk> wrote: |
| 6 |
> > >> > On Sunday, 17 April 2022 14:54:50 -00 Rich Freeman wrote: |
| 7 |
> > >> >> Can't you just fix your USE flags with systemd-utils? Why revert? |
| 8 |
> > >> > |
| 9 |
> > >> > No, because the flag I'd need is 'boot', and that triggers switching |
| 10 |
> > >> > from |
| 11 |
> > >> > elogind to systemd. |
| 12 |
> > >> |
| 13 |
> > >> No, USE=boot for systemd-util does not trigger anything like that. |
| 14 |
> > > |
| 15 |
> > > I meant, if I set that flag, portage wants me to remove elogind |
| 16 |
> > > andinstall |
| 17 |
> > > systemd. |
| 18 |
> > |
| 19 |
> > Maybe, but the fault is certainly not this flag but something else. |
| 20 |
> > For instance, that you do not have keyworded something which you should |
| 21 |
> > have. |
| 22 |
> It would probably be helpful to post more relevant output, like |
| 23 |
> portage output including --verbose and so on so that it is clear what |
| 24 |
> it is actually doing. |
| 25 |
> |
| 26 |
> systemd-utils blocks systemd, so I can't see how it could force you to |
| 27 |
> install systemd (after all, it just supplies things that are otherwise |
| 28 |
> bundled with systemd already). Maybe in addition to setting the boot |
| 29 |
> USE flag you also changed something else? |
| 30 |
|
| 31 |
The machine is sick. I now have no mouse or keyboard after POST. They're fine |
| 32 |
in UEFI BIOS setup, and they're fine after the default kernel has finished |
| 33 |
booting - just not at boot menu time. |
| 34 |
|
| 35 |
:( |
| 36 |
|
| 37 |
-- |
| 38 |
Regards, |
| 39 |
Peter. |
Archives