From: unruh@invalid.ca
On 2017-04-24, bad sector wrote:
> On 04/23/2017 09:20 PM, William Unruh wrote:
>> On 2017-04-23, bad sector 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])
>>
>> 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.
>
> I have a usb wifi transceiver, normally it's plugged-in. When I boot
> Suse-13.2 via grub1 it just comes up in the NetworkManager in the
> System-Tray and starts working. The SAME instalation if booted via
> grub2 either by way of a menu or directly commanded (C-key bailout) it
> does NOT come up, and clicking the NetworkManager icon shows no hardware
> to configure. Beats the crap out of me, even the kernel arguments are
> the same. I just installed a freshie TW and sofar it's the same
> behaviour, I'm also going to let Debian do a grub2 setup to see what gives.
>
>
Ah. Some information. It is a usb dongle and you use Network Manager.
Do lsusb under both grub 1 and grub 2 after boot up. Do both see the usb
wireless dongle.
Do lsmod under both. Is there ia difference in the modules loaded?
Do wpa_supplicant
and then iwlist
under both. DO you see something?
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
