From: malcolmlewis@cableone.net.invalid   
      
   On Fri, 16 Nov 2018 21:57:00 -0500   
   bad sector  wrote:   
      
   > On 11/16/18 9:04 PM, Malcolm wrote:   
   > > On Fri, 16 Nov 2018 20:33:45 -0500   
   > > bad sector  wrote:   
   > >   
   > >> On 11/14/18 12:03 PM, Malcolm wrote:   
   > >>   
   > >>> systemctl set-default multi-user.target   
   > >>> systemctl reboot   
   > >>>   
   > >>> login, switch to root user   
   > >>>   
   > >>> systemctl isolate graphical.target   
   > >>   
   > >> I'd be curious to know exactly what the above accomplishes and how   
   > >> to reverse it if required. I now have a situation which may be   
   > >> more than what IT gave me: I cannot boot at all from the grub   
   > >> menu, it leads to a panic stop. But if I boot manually following a   
   > >> Cntrl-C, new kernel or the previous one, then I can log in as user   
   > >> and do startx with no further issues.   
   > >>   
   > > Hi   
   > > So in SysVinit multi-user is runlevel 3 graphical is runlevel 5   
   > >   
   > > AFAIK init 3 and 5 still work.   
   > >   
   > > The isolate is the same as startx/init 5, to switch back to console,   
   > > would use isolate multi-user.target which will shutdown the X   
   > > server.   
   >   
   > thanks, so these are commands with no permanent effect, same as their   
   > equivalents, and have nothing to do with the inabilty of a grub boot   
   > which is another issue   
   >   
   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...   
      
   --   
   Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)   
   SLES 15 | GNOME Shell 3.26.2 | 4.12.14-25.25-default   
   HP 255 G4 Notebook | E2-7110 X4 @ 1.80 GHz | AMD Radeon R3   
   up 15 days 7:17, 2 users, load average: 0.09,   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)