home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   alt.os.linux.suse      Suse is actually not that bad      138,051 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 136,269 of 138,051   
   William Unruh to bad sector   
   Re: grub2 & wifi issue (1/10)   
   24 Apr 17 01:20:11   
   
   From: unruh@invalid.ca   
      
   On 2017-04-23, bad sector  wrote:   
   > On 04/23/2017 07:35 AM, Carlos E.R. wrote:   
   >> 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?   
   >   
   > Usually quite a few, depending on the disk(s) plugged-in   
   >   
   >> 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.   
   >   
   > 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])   
      
   I also do not understand what you mean by "no wifi". Is the driver   
   module not installed (lsmod) or is it just that wifi is not yet connected.   
      
   Wwhat are you using to connect with wifi.   
      
   I have no idea how something like grub2 can have anything to do with the   
   wifi.   
      
      
      
   >   
   >   
   >>>>> 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"   
   >   
   >   
   >> Post full /boot/grub/menu.lst and and /boot/grub2/grub.cfg   
   >   
   > This is the grub1 "mygrubs.txt" menu file in use this morning.   
   > NB. my problem with grub1 is that it cannot boot TW, and my problem with   
   > grub2 is that it cannot boot one of two 13.2 installations at all from   
   > menu (it's NOT in the menu) and when it boots the other one from themenu   
   > or either one from command line then the wifi is dead.   
   >   
   >   
   >   
   > #Grub-0.9x menu file: Disks AND partitions begin with 0 !!   
   > color black/red yellow/black   
   > #color white/blue yellow/black   
   > #color yellow/black white/green   
   > #color black/green yellow/black   
   > #color cyan/black white/blue   
   > #color magenta/black white/blue   
   > default 0    # default is first entry (starts with 0, no boot)   
   > #timeout 3000 # autoboot in ... seconds   
   > ######################### grub screen width scale   
   > ############################   
   > #   
   > #   
   > title    THIS menu file is @ /sda6/mygrubs.txt  On installed LINUX systems:   
   >           root   
   > title    visitor login & password = "visit", if required enter "startx"   
   >           root   
   >   
   > title    /dev/sda1             Win-7                      NTFS   
   >           unhide (hd0,0)   
   >           rootnoverify (hd0,0)   
   >           makeactive   
   >           chainloader (hd0,0)+1   
   >   
   > title    /dev/sda2        TumbleWeed               Kde5    xt4   
   >           root    (hd0,1)   
   >           #kernel  /boot/vmlinuz root=/dev/sda2   
   >           #kernel  /boot/vmlinuz-4.10.8-1-default root=/dev/sda2   
   >           kernel  /boot/vmlinuz-4.10.9-1-default root=/dev/sda2   
   >           initrd  /boot/initrd   
   >   
   > title    /dev/sda3    Slackware-14.1               Kde4    xt4   
   >           root	 (hd0,2)   
   >           kernel	 /boot/vmlinuz root=/dev/sda3 splash=0 3   
   >           #initrd /boot/initrd   
   >   
   > title    /dev/sda7          Mageia-5                       xt4   
   >           root	 (hd0,6)   
   >           kernel	 /boot/vmlinuz root=/dev/sda7 nokmsboot splash=0 3   
   >           initrd	 /boot/initrd   
   >   
   > title	 /dev/sda8        Debian-AvL                       xt4   
   >           root    (hd0,7)   
   >           kernel  /boot/vmlinuz root=/dev/sda8 splash=0 3   
   >           initrd  /boot/initrd   
   >   
   > title    /dev/sda9         Suse-13.2               Kde4    xt4   
   >           root	 (hd0,8)   
   >           kernel	 /boot/vmlinuz root=/dev/sda9 splash=0   
   >           initrd	 /boot/initrd   
   >   
   > title    Boot STERILE manually after PHYSICAL disconnect from networks   
   >           root   
   >   
   > title    /dev/sda10  STERILE  TumbleWeed          Kde5    xt4   
   >           root     (hd0,9)   
   >           #kernel  /boot/vmlinuz root=/dev/sda10 splash=0   
   >           #initrd  /boot/initrd   
   >   
   > title    /dev/sda11   STERILE  Slackware                  xt4   
   >           root      (hd0,10)   
   >           #kernel   /boot/vmlinuz root=/dev/sda10 splash=0   
   >           ##initrd  /boot/initrd   
   >   
   > title	 /dev/sda12   STERILE     Mageia                 TEST   
   >           root    (hd0,11)   
   >           #kernel  /boot/vmlinuz root=/dev/sda12 splash=0   
   >           #initrd  /boot/initrd   
   >   
   > title	 /dev/sda13   STERILE     Debian   
   >           root    (hd0,12)   
   >           #kernel  /boot/vmlinuz root=/dev/sda13   
      
   [continued in next message]   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca