On Sunday, 17 April 2022 20:17:47 -00 Rich Freeman wrote: > On Sun, Apr 17, 2022 at 1:05 PM Martin Vaeth <mar...@mvath.de> wrote: > > Peter Humphrey <pe...@prh.myzen.co.uk> wrote: > > > On Sunday, 17 April 2022 16:42:35 -00 Martin Vaeth wrote: > > >> Peter Humphrey <pe...@prh.myzen.co.uk> wrote: > > >> > On Sunday, 17 April 2022 14:54:50 -00 Rich Freeman wrote: > > >> >> Can't you just fix your USE flags with systemd-utils? Why revert? > > >> > > > >> > No, because the flag I'd need is 'boot', and that triggers switching > > >> > from > > >> > elogind to systemd. > > >> > > >> No, USE=boot for systemd-util does not trigger anything like that. > > > > > > I meant, if I set that flag, portage wants me to remove elogind > > > andinstall > > > systemd. > > > > Maybe, but the fault is certainly not this flag but something else. > > For instance, that you do not have keyworded something which you should > > have. > It would probably be helpful to post more relevant output, like > portage output including --verbose and so on so that it is clear what > it is actually doing. > > systemd-utils blocks systemd, so I can't see how it could force you to > install systemd (after all, it just supplies things that are otherwise > bundled with systemd already). Maybe in addition to setting the boot > USE flag you also changed something else?
The machine is sick. I now have no mouse or keyboard after POST. They're fine in UEFI BIOS setup, and they're fine after the default kernel has finished booting - just not at boot menu time. :( -- Regards, Peter.
