From: robin_listas@es.invalid   
      
   On 2017-04-23 07:34, bad sector wrote:   
   > On 04/23/2017 12:19 AM, Carlos E.R. wrote:   
   >> On 2017-04-23 06:00, bad sector wrote:   
   >>> On 04/22/2017 08:38 AM, Carlos E.R. wrote:   
   >>>> On 2017-04-22 03:37, bad sector wrote:   
   >>>>>   
   >>>>> I installed a fresh TW the other day which   
   >>>>> grub-1   
   >>>>   
   >>>> Why and how do you install with grub 1? It is not supported.   
   >>>   
   >>> I commanded grub-1 from a 13.2 installation to deploy boot code to the   
   >>> disk root on which 12 other linux OS's live, including 2 TW's.   
   >>   
   >> This paragraph is impossible to understand.   
   >   
   > WHAT do you not understand?   
   >   
   > I commanded grub-1 from a 13.2 installation:   
   > ============================================   
      
   What is the meaning of "I commanded"?   
      
      
   > Booted 13.2 cLi as-root   
   > # grub   
      
      
   How can you boot a CLI?   
      
   You boot Linux. Then you start the CLI. Or the GUI.   
      
      
      
      
   > deploy boot code to the disk root:   
   > ==================================   
   >   
   > grub > install (hd0,5)/stage1 (hd0) (hd0,5),stage2 p (hd0,5)/mygrubs.txt   
   >   
   >   
   >> Unless you explain and describe your setup *clearly*, I can not help you.   
   >>   
   >> Anyway: YaST on 13.2 can not install grub 1.   
   >> openSUSE installs grub2 since years.   
   >   
   > it's installed on 13.2, maybe not by yast   
   > or the installer, maybe that's why it works :-)   
   >   
   > Grub-2 is installed during installation on TW   
   > and the 13.2 installation booted that way   
   > results in the wifi being dead   
      
   You are mixing words for TW and 13.2, it is not clear what you are doing   
   where, or what the relation is. Do you have several systems installed?   
   Are you trying to boot one from another? Where is grub installed on each   
   one, and which version?   
      
      
   >>>>> can not boot no matter what partition   
   >>>>> it's on. So I try grub2 and the setup results   
   >>>>> in the predictable horror show for a menu   
   >>>>> but the command line works ok.   
   >>>>   
   >>>> I don't understand your problem with grub 2.   
   >>>> Just let the installer do its work and don't try to outsmart it.   
   >>>   
   >>> When I boot a 13.2 installation with grub-2 the wifi is dead, if I boot   
   >>> the same installation with grub-1, using essentially the same kernel   
   >>> arguments, then the wifi is up with problems-none on boot.   
   >>   
   >> You are not using the same kernel arguments.   
   >   
   >   
   > other than splash=0 which is irrelevant   
   >   
   > linux    /boot/vmlinuz root=/dev/sda9   
   >   
   > kernel   /boot/vmlinuz root=/dev/sda9   
   >   
   > what's the difference between   
   >   
   > /boot/vmlinuz root=/dev/sda9   
   >   
   > and   
   >   
   > /boot/vmlinuz root=/dev/sda9   
      
   That's not a grub2 line.   
      
      
   Post full /boot/grub/menu.lst and and /boot/grub2/grub.cfg   
      
    /var/log/messages.   
      
   And:   
      
   grep "Command line" /var/log/messages   
      
   --   
   Cheers, Carlos.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)