From: robin_listas@es.invalid   
      
   On 2017-04-24 00:31, bad sector wrote:   
   > On 04/23/2017 07:35 AM, Carlos E.R. wrote:   
      
      
   > It's the TW installer that installed grub2 on TW, and then when grub2   
   > boots a 13.2 installation on another partition it comes up with no wifi.   
   > If I then command grub2 directlty in a cLi (hit "C") it does the same   
   > thing. The only way I can boot any one of two 13.2 installations so that   
   > wifi will be up and ready is with grub1. Grub1 is installed on every   
   > installation except where it is inmpossible to install (I have not tried   
   > to install it to TW [yet])   
      
      
   So, we are talking of the grub2 installation done by TW, which defines   
   an auxiliary entry for 13.2 via os-prober. And you say that if you use   
   this one for 13.2, then it comes up with no wifi.   
      
   Finally we are getting some data.   
      
      
   Why don't you disable os-prober, and then create entries in   
   /boot/grub2/custom.cfg so that it chainloads grub1 of your 13.2 install?   
      
   (watch for line wrap after --set=root)   
      
      
   # If you change this file, run 'grub2-mkconfig -o /boot/grub2/grub.cfg'   
   # afterwards to update /boot/grub2/grub.cfg.   
      
   menuentry 'Chain: oS 13.2 (Harlequin) (on /dev/sda9)' {   
       insmod part_msdos   
       insmod ext2   
       set root='hd0,msdos9'   
       if search --no-floppy --fs-uuid --set=root   
   489842fe-6737-4682-8c50-8e25c10b746a ; then   
           chainloader +1   
       else   
           echo Could not find this OS instance, will not boot (3)   
           sleep 1   
       fi   
   }   
      
      
   menuentry 'Chain: oS 13.2 (Harlequin) (on /dev/sda12)' {   
       insmod part_msdos   
       insmod ext2   
       set root='hd0,msdos12'   
       if search --no-floppy --fs-uuid --set=root   
   489842fe-6737-4682-8c50-8e25c10b746a ; then   
           chainloader +1   
       else   
           echo Could not find this OS instance, will not boot (3)   
           sleep 1   
       fi   
   }   
      
      
   The above assumes that grub 2 or grub 1 of 13.2 is installed at the root   
   partition of the one which UUID is 489842fe-6737-4682-8c50-8e25c10b746a,   
   otherwise it will fail. It does not care which kernel, if any, is there.   
      
      
      
   >   
   >   
   >>>>> 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.   
   >   
   > The grub2 command is   
   >   
   >   "linux"   
   >   
   > The argument for the grub2 "linux" is   
   >   
   >   "/boot/vmlinuz root=/dev/sda9"   
      
      
      
   Notice that your entry for 'openSUSE 13.2 (Harlequin) (x86_64) (on   
   /dev/sda9)' has:   
      
    linux /boot/vmlinuz root=/dev/sda3 splash=0 3   
      
   not sda9. Doesn't really matter, what is crucial is the UUID. But it   
   boots on level 3, so perhaps NM does not start.   
      
      
   In fact, I see several menu entries that claim to boot /dev/sda9:   
      
   menuentry '/dev/sda7 Mageia-5 Hangs xt4 (on /dev/sda9)'   
           linux /boot/vmlinuz root=/dev/sda7 nokmsboot splash=0 3   
      
   menuentry '/dev/sda8 > Debian-AvL xt4 (on /dev/sda9)'   
           linux /boot/vmlinuz root=/dev/sda8 splash=0 3   
      
   menuentry '/dev/sda9 Suse-13.2 Kde4 xt4 (on /dev/sda9)'   
           linux /boot/vmlinuz root=/dev/sda9 splash=0   
      
   menuentry '/dev/sda13 was 2 tw > Ster-Deb (on /dev/sda9)'   
           linux /boot/vmlinuz root=/dev/sda13   
      
      
   So it is quite complicated to follow what is happening.   
      
   I suggest you post output of (watch for line wrap):   
      
   lsblk --output   
   NAME,KNAME,RA,RM,RO,SIZE,TYPE,FSTYPE,LABEL,PARTLABEL,MOUNTPOINT,   
   UID,PARTUUID,WWN,MODEL,ALIGNMENT   
      
      
      
   to confirm.   
      
      
      
   >>  /var/log/messages.   
   >>   
   >> And:   
   >>   
   >> grep "Command line" /var/log/messages   
   >   
   > on which system?   
      
   On the system that doesn't start wifi... 13.2.   
      
      
   > This is the grub.cfg on the TW system   
   > =====================================   
      
   Thanks. I took some data from this one to create custom.cfg above.   
      
   >   
   > it's pathetic, the script writingthis file seems to be reading menu   
   > files it can find instead of looking at what's in the partitions. It's a   
   > good thing I only had one of 4 disks plugged-into the rack.   
      
   It does look into the partitions.   
      
   --   
   Cheers, Carlos.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)