From: robin_listas@es.invalid   
      
   On 17/11/2018 12.52, bad sector wrote:   
   > On 11/17/18 4:56 AM, Carlos E.R. wrote:   
   >> On 17/11/2018 05.04, bad sector wrote:   
   >>> On 11/16/18 10:14 PM, Malcolm wrote:   
   >>>   
   >>>> Hi   
   >>>> Yup, did you try adding the grub option plymouth.enable=0 to   
   >>>> temporarily disable, also add console=tty to get it to the screen.   
   >>>> Those are temporary...   
   >>>   
   >>>   
   >>> No, where should I do that exactly?   
   >>>   
   >>> Meanwhile... I ran grub using Yast and had it deploy boot code to the   
   >>> disk root sector asper usual. Upon a reboot I got   
   >>>   
   >>> [FAILED] Failed to start Switch Root   
   >>> See 'systemctl status initrd-switch-root-.service' for details   
   >>> Enterig emergency mode...   
   >>   
   >> I don't even have that service installed, no idea what it does.   
      
   I see that I have it on another, older computer. But it is called   
   "initrd-switch-root.service", not "initrd-switch-root-.service".   
      
      
   >>> What is "linux-3f2q", the host name?  I changed it   
   >>> days ago to just m4. Finally why use initrd AT ALL?   
   >>   
   >> All openSUSE systems have an initrd archive or two. Your questions are   
   >> very strange...   
   >   
   > why?  Slackware never used initrd, still doesn't.   
      
   Well, that is the way it is designed.   
      
   If you really want no initrd, then either use another distro, or find   
   out why initrd is needed and work around all of the issues, manually,   
   yourself, to remove it. It is not a trivial pursuit and I can not really   
   guide you in that goal. There is someone on the mail list that does, though.   
      
   --   
   Cheers, Carlos.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)