Realtek RTL8821AE

[Sidney_Kotic]

I recently took possession of a custom built machine. It has a
MSI-X399-SLI-Plus motherboard and an AMD 2950x processor.

I've loaded Leap 15.0 onto it. But while it sees the PCI WiFi it won't use it.
I see the message:
rtl8821ae: Polling FW ready fail!! Pop up about every second in a terminal
windown (Ctrl F1).
I can use YaST and edit the device. Putting in all the correct information. It
will scan and show me the ESSID. But the device is always "Not connected".

What are my options? Is there a place I can go and download a device driver for
it? Should I go get an external WiFi adapter? If so, what kind?

[Malcolm]

Hi
Sounds like missing firmware, do you have the kernel-firmware package
installed?

find /lib/firmware/rtlwifi/rtl8821*

The output from the dmesg command should also provide further info.

--
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 21:55, 2 users, load average: 5.32,

[Sidney_Kotic]

On 12/11/18 2:44 PM, Malcolm wrote:

> find /lib/firmware/rtlwifi/rtl8821*

l /lib/firmware/rtlwifi/rtl8821*
-rw-r--r-- 1 root root 28984 Apr 16 2018 rtl8821aefw.bin
-rw-r--r-- 1 root root 28348 Apr 16 2018 rtl8821aefw_29.bin
-rw-r--r-- 1 root root 19858 Apr 16 2018 rtl8821aefw_wowlan.bin

> The output from the dmesg command should also provide further info.

dmesg | grep rtl | less

[ 9.698523] rtl8821ae 0000:05:00.0: enabling device (0000 -> 0003)
[ 9.710512] rtl8821ae: Using firmware rtlwifi/rtl8812aefw.bin
[ 9.710514] rtl8821ae: Using firmware rtlwifi/rtl8812aefw_wowlan.bin
[ 9.890890] rtl8821ae 0000:05:00.0: Direct firmware load for
rtlwifi/rtl8812aefw.bin failed with error -2
[ 9.897030] rtl8821ae 0000:05:00.0: Direct firmware load for
rtlwifi/rtl8812aefw_wowlan.bin failed with error -2
[ 9.929155] rtlwifi: Loading alternative firmware rtlwifi/rtl8821aefw.bin
[ 9.929162] rtlwifi: Loading alternative firmware rtlwifi/rtl8821aefw.bin
[ 10.062175] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
[ 10.062435] rtlwifi: rtlwifi: wireless switch is on
[ 15.513165] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .

[Malcolm]

Hi
It looks like a kernel issue, as in fixes are in a later version, if
you fire up a Live Tumbleweed version, does it start working?

--
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 23:39, 2 users, load average: 4.74,

[Sidney_Kotic]

On 12/11/18 4:27 PM, Malcolm wrote:

> It looks like a kernel issue, as in fixes are in a later version, if
> you fire up a Live Tumbleweed version, does it start working?

Downloaded openSUSE-Tumbleweed-KDE-Live-x86_64-Snapshot20181208-Media.iso
Burned a DVD.

Here's what Leap_15 says using the "ip a" command.
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen
1000
link/ether 30:9c:23:60:da:33 brd ff:ff:ff:ff:ff:ff
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group
default qlen 1000
link/ether f4:28:53:18:42:7e brd ff:ff:ff:ff:ff:ff

And this is the live.
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp8s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN
group default qlen 1000
link/ether 30:9c:23:60:da:33 brd ff:ff:ff:ff:ff:ff
3: wlp5s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN
group default qlen 1000
link/ether 5a:53:44:46:06:1d brd ff:ff:ff:ff:ff:ff

Both of which are no bueno.

[Malcolm]

Hi
It's not soft blocked, check with the output from the command;

rfkill list

Else it might be bug report time...

--
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 17 days 16:40, 2 users, load average: 3.27,

[Sidney_Kotic]

On 12/13/18 9:28 AM, Malcolm wrote:

> It's not soft blocked, check with the output from the command;
>
> rfkill list

0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

> Else it might be bug report time...

I guess, so where would I start with this process?

[Malcolm]

Hi
Start here;

http://en.opensuse.org/openSUSE:Submitting_bug_reports

Once created, post back the bug number ;)

--
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 17 days 17:33, 2 users, load average: 0.33,

[Sidney_Kotic]

On 12/13/18 10:20 AM, Malcolm wrote:

> Once created, post back the bug number ;)

Hope I gave the powers that be enough. The magic number is 1119574

The interesting thing is...Is it a rtl8812 or a rtl8821? A quick look around on
the web indicates this has been an ongoing question.

[Sidney_Kotic]

I should have asked them to be gentle with me. It's my first time.

[Sidney_Kotic]

Seems this has been assigned, if at all, to the back burner*.

So, in the meantime...thoughts on getting an external WiFi device? I'm not
familiar enough with things to know if that's even a viable option, perhaps the
whole networking procedure is dead and nothing I do will change that.

*Humorously I can say that, without networking, what I have is a really
expensive electric heater.

[Malcolm]

Hi
I use a mini router that connects to ethernet (I'm guess your board has
that?) then can also power over USB, use it for all sorts of things
since it has a USB port for storage printer etc... GPIO pins for
whatever, connect with minicom over the same cables used to connect
to my RPI's. I have one setup as a WiFi extender as well.

https://www.gl-inet.com/products/gl-mt300n/

--
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 4:55, 2 users, load average: 1.29, 1.22, 0.73

[Sidney_Kotic]

>> Seems this has been assigned, if at all, to the back burner.

Well, now I have a dilemma. The Leap 15.0, and Tumbleweed Live (12/8/2018) fail
to bring up the network. However, Ubuntu 18.10 fired off and promptly brought
up the network. Out of the box it also seems to understand the nvidia card
better, which really was something I figured on working on after the network
came live and I could get things to make it all better.

So, do I cut across to Ubuntu or not? I'd really rather not, but if I do that
means I'd have to replicate it on the other 4 computers currently running Leap
15.0, being a simple minded guy.

Do you know if there might be words of encouragement falling out of the inner
circle?

[Carlos E.R.]

On 18/12/2018 20.02, Sidney_Kotic wrote:
> Seems this has been assigned, if at all, to the back burner*.
>
> So, in the meantime...thoughts on getting an external WiFi device?  I'm
> not familiar enough with things to know if that's even a viable option,
> perhaps the whole networking procedure is dead and nothing I do will
> change that.

That should be a possibility. It can be a wifi dongle over USB,
investigating first which are known to work.

Once I purchased such a dongle, really tiny. It worked, but it could
hang easily, so instead I put a long ethernet cable.

Another possibility is to use a wifi to Ethernet "box". I don't know how
to call that: reverse access point?

--
Cheers, Carlos.

[Carlos E.R.]

On 01/01/2019 04.11, Sidney_Kotic wrote:
>>> Seems this has been assigned, if at all, to the back burner.
>
> Well, now I have a dilemma.  The Leap 15.0, and Tumbleweed Live
> (12/8/2018) fail to bring up the network.  However, Ubuntu 18.10 fired
> off and promptly brought up the network.

IMO, you should add that information on the bugzilla. Maybe compare the
stacks on both setups, find out what they do differently.

> Out of the box it also seems
> to understand the nvidia card better, which really was something I
> figured on working on after the network came live and I could get things
> to make it all better.

I suspect that Ubuntu doesn't care about certain legal issues.

I have an Nvidia card, it works fine. I just install the nvidia rpms
available at the nvidia site. It was trivial easy. Years ago it was more
difficult.

However, there are some cases where things fail. For instance, some
laptops with optimus hardware have it almost impossible.

>
> So, do I cut across to Ubuntu or not?  I'd really rather not, but if I
> do that means I'd have to replicate it on the other 4 computers
> currently running Leap 15.0, being a simple minded guy.

Well, have those other computers the same problematic wifi hardware?

Historically, hardware that needs loading firmware from the computer are
a huge pain. I hate them. I had one or two modems that would not work on
Linux, only Windows. Winprinters are another example. Well, some of
those do not load firmware, but need software helpers running on the
host, because their CPUs are not powerful enough.

>
> Do you know if there might be words of encouragement falling out of the
> inner circle?

Bugzilla solving happens slowly, depending on how many people are
affected, severity, volunteer solvers... You have to be patient.

I don't know if "network" is the appropriate component for that
Bugzilla. Might be "kernel". Malcolm?

--
Cheers, Carlos.

[Malcolm]

Hi
Can you post the output from the command usb-devices in Ub* or
whichever tool is used to show the usb device and driver in use?

Then in the output from the driver name run the command;

modinfo <driver_name>

This will show info on any firmware files in use, which may be missing
on the openSUSE side....

The output from dmesg as well for the device....

--
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 6 days 22:20, 2 users, load average: 0.12,

[Sidney_Kotic]

Here's what I scraped off of the machine. There doesn't appear to be a hwinfo
command. But I found something close, lshw.

cat /etc/os-release
NAME="Ubuntu"
VERSION="18.10 (Cosmic Cuttlefish)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.10"
VERSION_ID="18.10"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=cosmic
UBUNTU_CODENAME=cosmic
=============================================

ip a

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp8s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN
group default qlen 1000
link/ether 30:9c:23:60:da:33 brd ff:ff:ff:ff:ff:ff

3: wlp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group

default qlen 1000
link/ether f4:28:53:18:42:7e brd ff:ff:ff:ff:ff:ff

inet 172.16.2.46/24 brd 172.16.2.255 scope global dynamic noprefixroute wlp5s0
valid_lft 75711sec preferred_lft 75711sec
inet6 fe80::ae82:a4d5:4047:3474/64 scope link noprefixroute
valid_lft forever preferred_lft forever
==============================================

iwconfig
lo no wireless extensions.

enp8s0 no wireless extensions.

wlp5s0 IEEE 802.11 ESSID:"A valid place to connect to"
Mode:Managed Frequency:2.462 GHz Access Point: 82:2A:A8:A1:62:3E
Bit Rate=1 Mb/s Tx-Power=20 dBm
Retry short limit:7 RTS thr=2347 B Fragment thr:off
Power Management:on
Link Quality=70/70 Signal level=-38 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:6935 Missed beacon:0
==================================================

dmesg | grep rtl
[ 10.119684] rtl8821ae 0000:05:00.0: enabling device (0000 -> 0003)
[ 10.132198] rtl8821ae: Using firmware rtlwifi/rtl8812aefw.bin
[ 10.132201] rtl8821ae: Using firmware rtlwifi/rtl8812aefw_wowlan.bin
[ 10.170523] rtl8821ae 0000:05:00.0: Direct firmware load for

rtlwifi/rtl8812aefw_wowlan.bin failed with error -2

[ 10.170616] rtl8821ae 0000:05:00.0: Direct firmware load for

rtlwifi/rtl8812aefw.bin failed with error -2

[ 10.272644] rtlwifi: Loading alternative firmware rtlwifi/rtl8821aefw.bin
[ 10.272650] rtlwifi: Loading alternative firmware rtlwifi/rtl8821aefw.bin
[ 10.312415] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
[ 10.312740] rtlwifi: rtlwifi: wireless switch is on
[ 10.361653] rtl8821ae 0000:05:00.0 wlp5s0: renamed from wlan0
[ 20.703442] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .
[ 22.175911] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .
=================================================

rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

==================================================

lspci -nnk | grep -iA3 net
05:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8812AE
802.11ac PCIe Wireless Network Adapter [10ec:8812] (rev 01)
Subsystem: Realtek Semiconductor Co., Ltd. RTL8812AE 802.11ac PCIe
Wireless Network Adapter [10ec:0812]
Kernel driver in use: rtl8821ae
Kernel modules: rtl8821ae
08:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network
Connection [8086:1539] (rev 03)
Subsystem: Micro-Star International Co., Ltd. [MSI] I211 Gigabit
Network Connection [1462:7b09]
Kernel driver in use: igb
Kernel modules: igb
0a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD]
Device [1022:145a]
================================================================

modinfo rtl8821ae
filename:
/lib/modules/4.18.0-13-generic/kernel/drivers/net/wireless/realtek/rtlwifi/rtl8821ae/rtl8821ae.ko
firmware: rtlwifi/rtl8821aefw_29.bin
firmware: rtlwifi/rtl8821aefw.bin
description: Realtek 8821ae 802.11ac PCI wireless
license: GPL
author: Realtek WlanFAE <wla...@realtek.com>
srcversion: 3431C83A08FDABA185BFB17
alias: pci:v000010ECd00008821sv*sd*bc*sc*i*
alias: pci:v000010ECd00008812sv*sd*bc*sc*i*
depends: rtlwifi,rtl_pci,btcoexist,mac80211
retpoline: Y
intree: Y
name: rtl8821ae
vermagic: 4.18.0-13-generic SMP mod_unload
sig_id: PKCS#7
signer:
sig_key:
sig_hashalgo: md4
signature: 30:82:02:A5:06:09:2A:86:48:86:F7:0D:01:07:02:A0:82:02:96:30:
82:02:92:02:01:01:31:0D:30:0B:06:09:60:86:48:01:65:03:04:02:
03:30:0B:06:09:2A:86:48:86:F7:0D:01:07:01:31:82:02:6F:30:82:
02:6B:02:01:01:30:46:30:2E:31:2C:30:2A:06:03:55:04:03:0C:23:
42:75:69:6C:64:20:74:69:6D:65:20:61:75:74:6F:67:65:6E:65:72:
61:74:65:64:20:6B:65:72:6E:65:6C:20:6B:65:79:02:14:40:71:35:
68:4F:B5:09:52:A4:1C:79:66:D0:19:CB:22:FE:F8:0B:19:30:0B:06:
09:60:86:48:01:65:03:04:02:03:30:0D:06:09:2A:86:48:86:F7:0D:
01:01:01:05:00:04:82:02:00:73:09:56:8D:0A:60:5C:09:EE:01:ED:
5B:56:75:15:3B:8E:3D:94:5E:5F:A0:C5:8D:91:21:35:6C:4F:DF:BC:
21:53:E7:A9:FF:1C:D8:A1:55:F9:BD:89:BA:7B:2F:8E:81:F8:99:78:
B6:8E:09:5D:CE:22:AA:1C:68:8D:A9:74:55:06:C4:8F:46:80:DA:CF:
F1:57:84:5C:B1:C4:C4:12:E4:7F:A6:DB:F9:3A:09:7A:6B:EA:0F:9D:
EF:B4:92:CD:8C:6B:08:21:F7:72:BA:3C:31:39:EF:25:87:8D:A7:6A:
EC:EB:FD:CA:3D:D2:C0:F7:02:C9:A5:5C:F9:75:B4:3A:DC:38:96:0B:
EB:05:6B:03:60:DD:92:CF:51:10:AA:20:DD:85:DF:B4:F2:18:96:14:
8E:87:1D:43:91:B3:00:FE:8B:E6:FA:B4:CF:34:83:3B:05:D0:9B:C9:
B3:93:AF:77:3D:6D:CD:33:BC:59:94:7D:0B:49:82:09:89:20:A8:47:
E9:2D:F6:0F:E0:1F:38:49:A9:E0:83:38:70:C9:5D:18:80:C1:C7:C4:
55:CD:27:F5:58:D0:DC:2F:C5:1B:F7:DC:4F:EB:38:93:4C:8E:7F:85:
46:E8:51:D3:8A:90:65:89:56:33:70:15:52:A2:60:4B:71:4B:CC:95:
BE:F9:15:4B:D9:3C:9C:2E:13:78:89:35:AB:C9:7E:1F:C4:FB:A5:5A:
EC:26:BC:FC:71:9E:D2:B2:65:85:1E:3A:F4:89:97:60:56:28:3F:58:
E0:F5:58:6F:4D:71:B1:71:AE:32:7D:9D:BD:CC:11:3B:1E:39:A9:59:
25:27:1B:F3:B3:77:0B:BC:D8:7D:31:38:9C:71:AC:AE:BC:BC:83:C6:
D4:B6:EF:E5:BF:75:F6:1F:6A:1A:EE:C3:F6:46:19:1F:2E:C3:FF:52:
CC:C5:00:B4:B5:48:5D:9A:61:6B:F4:1F:B8:F3:25:40:6A:08:9B:07:
AB:09:48:9E:9D:BA:4A:57:26:78:D3:17:F1:9C:3F:A9:CC:A3:08:18:
A9:B2:93:11:B6:67:89:C0:A5:EB:D3:F8:BB:6D:21:5B:AE:ED:7F:59:
F9:00:ED:12:9D:EC:83:5E:54:C8:36:99:09:9D:1D:34:E3:7B:69:CF:
BD:B1:5D:A3:A1:36:07:E2:9D:05:7D:5D:2F:BE:C1:B4:24:87:FA:32:
CB:99:CA:76:69:4A:D4:47:5B:29:25:7D:91:B5:6C:C2:53:13:54:A4:
08:62:5E:1D:DD:07:3A:5C:45:B6:F5:03:85:A3:C0:67:EE:95:E4:D4:
A9:C4:D0:03:7A:A3:5A:E8:50:8B:87:30:30:65:2B:8A:EC:56:DF:C8:
C9
parm: swenc:Set to 1 for software crypto (default 0)
(bool)
parm: ips:Set to 0 to not use link power save (default 1)
(bool)
parm: swlps:Set to 1 to use SW control power save (default 0)
(bool)
parm: fwlps:Set to 1 to use FW control power save (default 1)
(bool)
parm: msi:Set to 1 to use MSI interrupts mode (default 1)
(bool)
parm: aspm:Set to 1 to enable ASPM (default 1)
(int)
parm: debug_level:Set debug level (0-5) (default 0) (int)
parm: debug_mask:Set debug mask (default 0) (ullong)
parm: disable_watchdog:Set to 1 to disable the watchdog (default 0)
(bool)
parm: int_clear:Set to 0 to disable interrupt clear before set (default 1)
(bool)
======================================================

lshw -short
H/W path Device Class Description
=======================================================
system MS-7B09 (To be filled by O.E.M.)
/0 bus X399 SLI PLUS (MS-7B09)
/0/0 memory 64KiB BIOS
/0/f memory 16GiB System Memory
/0/f/0 memory 2667 MHz (0.4 ns) [empty]
/0/f/1 memory 8GiB DIMM DDR4 Synchronous
Unbuffered (Unregistered) 2667 MHz (0.4 ns)
/0/f/2 memory 2667 MHz (0.4 ns) [empty]
/0/f/3 memory 8GiB DIMM DDR4 Synchronous
Unbuffered (Unregistered) 2667 MHz (0.4 ns)
/0/f/4 memory 2667 MHz (0.4 ns) [empty]
/0/f/5 memory 2667 MHz (0.4 ns) [empty]
/0/f/6 memory 2667 MHz (0.4 ns) [empty]
/0/f/7 memory 2667 MHz (0.4 ns) [empty]
/0/12 memory 1536KiB L1 cache
/0/13 memory 8MiB L2 cache
/0/14 memory 32MiB L3 cache
/0/15 processor AMD Ryzen Threadripper 2950X 16-Core
Processor
/0/100 bridge Family 17h (Models 00h-0fh) Root Complex
/0/100/0.2 generic Family 17h (Models 00h-0fh) I/O
Memory Management Unit
/0/100/1.1 bridge Family 17h (Models 00h-0fh) PCIe GPP
Bridge
/0/100/1.1/0 bus X399 Series Chipset USB 3.1 xHCI
Controller
/0/100/1.1/0.1 storage X399 Series Chipset SATA Controller
/0/100/1.1/0.2 bridge X399 Series Chipset PCIe Bridge
/0/100/1.1/0.2/0 bridge 300 Series Chipset PCIe Port
/0/100/1.1/0.2/0/0 bus ASMedia Technology Inc.
/0/100/1.1/0.2/2 bridge 300 Series Chipset PCIe Port
/0/100/1.1/0.2/3 bridge 300 Series Chipset PCIe Port
/0/100/1.1/0.2/3/0 wlp5s0 network RTL8812AE 802.11ac PCIe Wireless
Network Adapter
/0/100/1.1/0.2/4 bridge 300 Series Chipset PCIe Port
/0/100/1.1/0.2/5 bridge 300 Series Chipset PCIe Port
/0/100/1.1/0.2/6 bridge 300 Series Chipset PCIe Port
/0/100/1.1/0.2/6/0 enp8s0 network I211 Gigabit Network Connection
/0/100/1.1/0.2/7 bridge 300 Series Chipset PCIe Port
/0/100/7.1 bridge Family 17h (Models 00h-0fh) Internal
PCIe GPP Bridge 0 to Bus B
/0/100/7.1/0 generic Advanced Micro Devices, Inc. [AMD]
/0/100/7.1/0.2 generic Family 17h (Models 00h-0fh) Platform
Security Processor
/0/100/7.1/0.3 bus USB 3.0 Host controller
/0/100/8.1 bridge Family 17h (Models 00h-0fh) Internal
PCIe GPP Bridge 0 to Bus B
/0/100/8.1/0 generic Advanced Micro Devices, Inc. [AMD]
/0/100/8.1/0.2 storage FCH SATA Controller [AHCI mode]
/0/100/8.1/0.3 multimedia Family 17h (Models 00h-0fh) HD Audio
Controller
/0/100/14 bus FCH SMBus Controller
/0/100/14.3 bridge FCH LPC Bridge
/0/101 bridge Family 17h (Models 00h-0fh) PCIe
Dummy Host Bridge
/0/102 bridge Family 17h (Models 00h-0fh) PCIe
Dummy Host Bridge
/0/103 bridge Family 17h (Models 00h-0fh) PCIe
Dummy Host Bridge
/0/104 bridge Family 17h (Models 00h-0fh) PCIe
Dummy Host Bridge
/0/105 bridge Family 17h (Models 00h-0fh) PCIe
Dummy Host Bridge
/0/106 bridge Family 17h (Models 00h-0fh) PCIe
Dummy Host Bridge
/0/107 bridge Family 17h (Models 00h-0fh) Data
Fabric: Device 18h; Function 0
/0/108 bridge Family 17h (Models 00h-0fh) Data
Fabric: Device 18h; Function 1
/0/109 bridge Family 17h (Models 00h-0fh) Data
Fabric: Device 18h; Function 2
/0/10a bridge Family 17h (Models 00h-0fh) Data
Fabric: Device 18h; Function 3
/0/10b bridge Family 17h (Models 00h-0fh) Data
Fabric: Device 18h; Function 4
/0/10c bridge Family 17h (Models 00h-0fh) Data
Fabric: Device 18h; Function 5
/0/10d bridge Family 17h (Models 00h-0fh) Data
Fabric: Device 18h; Function 6
/0/10e bridge Family 17h (Models 00h-0fh) Data
Fabric: Device 18h; Function 7
/0/10f bridge Family 17h (Models 00h-0fh) Data
Fabric: Device 18h; Function 0
/0/110 bridge Family 17h (Models 00h-0fh) Data
Fabric: Device 18h; Function 1
/0/111 bridge Family 17h (Models 00h-0fh) Data
Fabric: Device 18h; Function 2
/0/112 bridge Family 17h (Models 00h-0fh) Data
Fabric: Device 18h; Function 3
/0/113 bridge Family 17h (Models 00h-0fh) Data
Fabric: Device 18h; Function 4
/0/114 bridge Family 17h (Models 00h-0fh) Data
Fabric: Device 18h; Function 5
/0/115 bridge Family 17h (Models 00h-0fh) Data
Fabric: Device 18h; Function 6
/0/116 bridge Family 17h (Models 00h-0fh) Data
Fabric: Device 18h; Function 7
/0/117 bridge Family 17h (Models 00h-0fh) Root Complex
/0/117/0.2 generic Family 17h (Models 00h-0fh) I/O
Memory Management Unit
/0/117/3.1 bridge Family 17h (Models 00h-0fh) PCIe GPP
Bridge
/0/117/3.1/0 display GP108 [GeForce GT 1030]
/0/117/3.1/0.1 multimedia GP108 High Definition Audio Controller
/0/117/7.1 bridge Family 17h (Models 00h-0fh) Internal
PCIe GPP Bridge 0 to Bus B
/0/117/7.1/0 generic Advanced Micro Devices, Inc. [AMD]
/0/117/7.1/0.2 generic Family 17h (Models 00h-0fh) Platform
Security Processor
/0/117/7.1/0.3 bus USB 3.0 Host controller
/0/117/8.1 bridge Family 17h (Models 00h-0fh) Internal
PCIe GPP Bridge 0 to Bus B
/0/117/8.1/0 generic Advanced Micro Devices, Inc. [AMD]
/0/117/8.1/0.2 storage FCH SATA Controller [AHCI mode]
/0/118 bridge Family 17h (Models 00h-0fh) PCIe
Dummy Host Bridge
/0/119 bridge Family 17h (Models 00h-0fh) PCIe
Dummy Host Bridge
/0/11a bridge Family 17h (Models 00h-0fh) PCIe
Dummy Host Bridge
/0/11b bridge Family 17h (Models 00h-0fh) PCIe
Dummy Host Bridge
/0/11c bridge Family 17h (Models 00h-0fh) PCIe
Dummy Host Bridge
/0/11d bridge Family 17h (Models 00h-0fh) PCIe
Dummy Host Bridge
/0/1 scsi2 storage
/0/1/0.0.0 /dev/cdrom disk BD-RE WH16NS40
/0/2 scsi6 storage
/0/2/0.0.0 /dev/sda disk 2TB ST2000DM006-2DM1
/0/2/0.0.0/1 volume 511MiB Windows FAT volume
/0/2/0.0.0/2 /dev/sda2 volume 1862GiB EXT4 volume
/0/3 scsi10 storage
/0/3/0.0.0 /dev/sdb disk 16GB USB 2.0 FD
/0/3/0.0.0/0 /dev/sdb disk 16GB
/0/3/0.0.0/0/1 /dev/sdb1 volume 14GiB Windows NTFS volume

[Sidney_Kotic]

> Well, have those other computers the same problematic wifi hardware?

Yes, and no. Two have USB dongle WiFi on them (known MB chipset
incompatibility), and two worked just fine out of the box. But, there's always
a but, 3 of them are at my condo. Two of them are here with me where I spend my
winters, the new one is included. At the condo I control the network all the
way to the cable outlet on the wall. Here...I'm just another one of the poor
schmucks barely connecting to a really poor WiFi setup.

[Carlos E.R.]

On 01/01/2019 20.01, Sidney_Kotic wrote:
> dmesg | grep rtl
> [   10.119684] rtl8821ae 0000:05:00.0: enabling device (0000 -> 0003)
> [   10.132198] rtl8821ae: Using firmware rtlwifi/rtl8812aefw.bin
> [   10.132201] rtl8821ae: Using firmware rtlwifi/rtl8812aefw_wowlan.bin
> [   10.170523] rtl8821ae 0000:05:00.0: Direct firmware load for
> rtlwifi/rtl8812aefw_wowlan.bin failed with error -2
> [   10.170616] rtl8821ae 0000:05:00.0: Direct firmware load for
> rtlwifi/rtl8812aefw.bin failed with error -2
> [   10.272644] rtlwifi: Loading alternative firmware
> rtlwifi/rtl8821aefw.bin
> [   10.272650] rtlwifi: Loading alternative firmware
> rtlwifi/rtl8821aefw.bin
> [   10.312415] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
> [   10.312740] rtlwifi: rtlwifi: wireless switch is on
> [   10.361653] rtl8821ae 0000:05:00.0 wlp5s0: renamed from wlan0
> [   20.703442] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .
> [   22.175911] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .

I see in my Leap machines:

/lib/firmware/rtlwifi/rtl8821aefw.bin

at least the file does exist. It comes in
kernel-firmware-20170530-23.1.noarch rpm (or
kernel-firmware-20180525-lp150.2.3.1.noarch in Leap 15.0)

--
Cheers, Carlos.

[Sidney_Kotic]

On 1/1/19 1:52 PM, Carlos E.R. wrote:

> I see in my Leap machines:
>
> /lib/firmware/rtlwifi/rtl8821aefw.bin
>
> at least the file does exist. It comes in
> kernel-firmware-20170530-23.1.noarch rpm (or
> kernel-firmware-20180525-lp150.2.3.1.noarch in Leap 15.0)
>

If I followed what you said correctly. The Leap 15.0 install/boot produced this:
dmesg | grep rtl | less

[ 9.711947] rtl8821ae 0000:05:00.0: enabling device (0000 -> 0003)
[ 9.723876] rtl8821ae: Using firmware rtlwifi/rtl8812aefw.bin
[ 9.723878] rtl8821ae: Using firmware rtlwifi/rtl8812aefw_wowlan.bin
[ 9.734091] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
[ 9.734277] rtlwifi: rtlwifi: wireless switch is on
[ 9.981853] rtl8821ae 0000:05:00.0: Direct firmware load for

rtlwifi/rtl8812aefw.bin failed with error -2

[ 10.121891] rtl8821ae 0000:05:00.0: Direct firmware load for

rtlwifi/rtl8812aefw_wowlan.bin failed with error -2

[ 10.158808] rtlwifi: Loading alternative firmware rtlwifi/rtl8821aefw.bin
[ 10.158816] rtlwifi: Loading alternative firmware rtlwifi/rtl8821aefw.bin
[ 15.651686] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .

And the network doesn't come up. But then I can be pretty dense at times.

[Carlos E.R.]

Compare with what you posted from Ubuntu:

> [ 10.119684] rtl8821ae 0000:05:00.0: enabling device (0000 -> 0003)
> [ 10.132198] rtl8821ae: Using firmware rtlwifi/rtl8812aefw.bin

> [ 10.132201] rtl8821ae: Using firmware rtlwifi/rtl8812aefw_wowlan.bin

> [ 10.170523] rtl8821ae 0000:05:00.0: Direct firmware load for rtlwifi/rtl8812aefw_wowlan.bin failed with error -2
> [ 10.170616] rtl8821ae 0000:05:00.0: Direct firmware load for rtlwifi/rtl8812aefw.bin failed with error -2
> [ 10.272644] rtlwifi: Loading alternative firmware rtlwifi/rtl8821aefw.bin
> [ 10.272650] rtlwifi: Loading alternative firmware rtlwifi/rtl8821aefw.bin
> [ 10.312415] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
> [ 10.312740] rtlwifi: rtlwifi: wireless switch is on
> [ 10.361653] rtl8821ae 0000:05:00.0 wlp5s0: renamed from wlan0
> [ 20.703442] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .
> [ 22.175911] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .

It is almost the same. Both fail at "polling".

I think you should compare more lines and find out when Ubuntu succeeds,
what is different. Don't filter the output with grep, just in case we
miss something important.

--
Cheers, Carlos.

[Sidney_Kotic]

On 1/1/19 7:09 PM, Carlos E.R. wrote:

> I think you should compare more lines and find out when Ubuntu succeeds,
> what is different. Don't filter the output with grep, just in case we
> miss something important.

I've produced two listings. I'll compare them, but want to say that I've not
spent time looking at boot logs since when I was taking care of VMS/Solaris
machines. In the meantime if you'd like to look they're at www.luddites.org/no-net

[Carlos E. R.]

I'll have a look tonight or tomorrow - I need my big desktop screen, not
this tiny laptop's :-)

--
Cheers,
Carlos E.R.

[Sidney_Kotic]

On 1/2/19 2:10 PM, Carlos E. R. wrote:

> I'll have a look tonight or tomorrow - I need my big desktop screen, not
> this tiny laptop's :-)

I haul an 8" kindle around when I'm traveling.

The first thing I noticed is that the ubuntu has a much newer kernel, built with
newer software. Second was that the source for the module was different. I was
going to see if there was a tumbleweed that had a kernel anywhere close, but
didn't see an easy way to check.

[Carlos E.R.]

Ok, I had a look.

This is the related leap log - long lines:


[ 0.000000] Linux version 4.12.14-lp150.11-default (geeko@buildhost) (gcc version 7.3.1 20180323 [gcc-7-branch revision 258812] (SUSE Linux) ) #1 SMP Fri May 11 08:28:30 UTC 2018 (a9fee09)
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.12.14-lp150.11-default root=UUID=c11db263-e476-4873-b7d9-3edc73db03f9 resume=/dev/disk/by-id/ata-ST2000DM006-2DM164_Z560XHT9-part4 splash=silent quiet showopts


[ 9.912797] rtl8821ae: Using firmware rtlwifi/rtl8812aefw.bin
[ 9.912800] rtl8821ae: Using firmware rtlwifi/rtl8812aefw_wowlan.bin
[ 9.952074] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
[ 9.952342] rtlwifi: rtlwifi: wireless switch is on
[ 10.003321] rtl8821ae 0000:05:00.0: Direct firmware load for rtlwifi/rtl8812aefw.bin failed with error -2
[ 10.003357] rtl8821ae 0000:05:00.0: Direct firmware load for rtlwifi/rtl8812aefw_wowlan.bin failed with error -2

[ 10.076173] rtlwifi: Loading alternative firmware rtlwifi/rtl8821aefw.bin
[ 10.076180] rtlwifi: Loading alternative firmware rtlwifi/rtl8821aefw.bin

[ 18.278133] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 18.323229] No iBFT detected.
[ 18.342261] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 18.633671] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .
[ 18.837320] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 18.851331] Ebtables v2.0 registered
[ 18.862209] NET: Registered protocol family 17
[ 19.024232] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
[ 19.219454] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ 19.316622] Netfilter messages via NETLINK v0.30.
[ 19.338529] ip_set: protocol 6
[ 19.821663] logitech-hidpp-device 0003:046D:4051.0004: HID++ 4.5 device connected.
[ 22.777395] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .
[ 31.197636] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .
[ 39.616262] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .
[ 48.035914] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .
[ 56.463634] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .
[ 64.936258] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .
[ 73.374907] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .
[ 81.806200] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .
[ 90.226206] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .
[ 98.177739] logitech-hidpp-device 0003:046D:2011.0005: HID++ 1.0 device connected.
[ 98.642995] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .
[ 107.068057] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .

[ 115.488017] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .

[ 123.911708] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .

[ 132.330544] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .

[ 140.761128] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .
[ 149.179538] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .
[ 157.599788] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .

[ 166.023989] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .

[ 174.443937] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .
[ 178.599996] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .



And this is the ubuntu log:

[ 0.000000] Linux version 4.18.0-10-generic (buildd@lgw01-amd64-060) (gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)) #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 (Ubuntu 4.18.0-10.11-generic 4.18.12)
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=7bd34b46-278a-4775-94a1-9d27a25f7f0f ro quiet splash vt.handoff=1


[ 10.591798] rtl8821ae: Using firmware rtlwifi/rtl8812aefw.bin
[ 10.591800] rtl8821ae: Using firmware rtlwifi/rtl8812aefw_wowlan.bin


[ 10.617072] rtl8821ae 0000:05:00.0: Direct firmware load for rtlwifi/rtl8812aefw_wowlan.bin failed with error -2
[ 10.617145] rtl8821ae 0000:05:00.0: Direct firmware load for rtlwifi/rtl8812aefw.bin failed with error -2
[ 10.632552] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
[ 10.632778] rtlwifi: rtlwifi: wireless switch is on
[ 10.739999] rtl8821ae 0000:05:00.0 wlp5s0: renamed from wlan0

[ 11.067774] rtlwifi: Loading alternative firmware rtlwifi/rtl8821aefw.bin
[ 11.067780] rtlwifi: Loading alternative firmware rtlwifi/rtl8821aefw.bin

[ 19.920931] IPv6: ADDRCONF(NETDEV_UP): enp8s0: link is not ready
[ 19.944887] IPv6: ADDRCONF(NETDEV_UP): enp8s0: link is not ready
[ 19.948813] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
[ 20.175287] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .
[ 20.378943] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
[ 21.421475] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
[ 21.548948] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .
[ 24.872954] wlp5s0: authenticate with 82:2a:a8:a1:62:3e
[ 24.873810] wlp5s0: send auth to 82:2a:a8:a1:62:3e (try 1/3)
[ 24.889073] wlp5s0: authenticated
[ 24.896151] wlp5s0: associate with 82:2a:a8:a1:62:3e (try 1/3)
[ 24.924465] wlp5s0: RX AssocResp from 82:2a:a8:a1:62:3e (capab=0x31 status=0 aid=7)
[ 24.929869] wlp5s0: associated
[ 25.232453] IPv6: ADDRCONF(NETDEV_CHANGE): wlp5s0: link becomes ready



The difference is after this line:

rtlwifi: Loading alternative firmware rtlwifi/rtl8821aefw.bin

initially, both fail:

U: [ 19.920931] IPv6: ADDRCONF(NETDEV_UP): enp8s0: link is not ready
L: [ 18.837320] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

Then, the difference:

Ubuntu:

[ 20.175287] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .
[ 20.378943] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
[ 21.421475] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
[ 21.548948] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .
[ 24.872954] wlp5s0: authenticate with 82:2a:a8:a1:62:3e

Leap:

[ 22.777395] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .
[ 31.197636] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .
[ 39.616262] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .
[ 48.035914] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .
[ 56.463634] rtl8821ae: Polling FW ready fail!! REG_MCUFWDL:0x00070706 .


Note that both have the same error, but Ubuntu authenticates with the network...
I suppose that after second 21, things work on Ubuntu.
There are 3 seconds of silence in the logs at that point.

My initial guess is that the firmware file (rtl8821aefw.bin) is different, you could compare them.
If that's not it, it is the kernel.
You should post this info on the bugzilla.


--
Cheers, Carlos.

[Carlos E.R.]

Yes, there is a repo with newer kernels that can be used on Leap:

<https://download.opensuse.org/repositories/Kernel:/stable/standard>

last time I looked, they have 4.19, so even newer than Ubuntu's.

--
Cheers, Carlos.

[Sidney_Kotic]

OK, it's gonna take a while. The ubuntu load is working, sorta, and I've got it
running some stuff. As soon as that clears out I'll attempt to split the drive
up and install ubuntu, leap, and tw on the drive. Right now when I install one
it gleefully deletes anything it can find and grabs the whole drive.

> Note that both have the same error, but Ubuntu authenticates with the network...
> I suppose that after second 21, things work on Ubuntu.
> There are 3 seconds of silence in the logs at that point.

As I said earlier, the wifi around here inhales. It could easily take much more
than 21 seconds to connect. It could take half an hour, and has. It's also
been longer than that.

> My initial guess is that the firmware file (rtl8821aefw.bin) is different, you could compare them.
> If that's not it, it is the kernel.
> You should post this info on the bugzilla.

Once I get things sort of straightened out I'll be back with results.

Thanks for your help.

[Sidney_Kotic]

On 1/3/19 8:37 AM, Carlos E.R. wrote:

> My initial guess is that the firmware file (rtl8821aefw.bin) is different, you could compare them.
> If that's not it, it is the kernel.
> You should post this info on the bugzilla.

There's few differences, other than date/time stamps. To wit:

leap
filename:
/lib/modules/4.12.14-lp150.11-default/kernel/drivers/net/wireless/realtek/rtlwifi/rtl8821ae/rtl8821ae.ko
srcversion: 1F9B1C2F3A41D8A2F8A60B3

ubuntu
filename:
/lib/modules/4.18.0-10-generic/kernel/drivers/net/wireless/realtek/rtlwifi/rtl8821ae/rtl8821ae.ko
srcversion: 3431C83A08FDABA185BFB17

leap sha256
11e7ea00504fa2fa6f5216bb59403c4f2f20eec5b676c0add0695db3b0c4a335 rtl8821aefw_29.bin
025c13f2e7f7526e1f932049bed2146467318f547ffa8481804ecfd911cda695 rtl8821aefw.bin
df6fe0f14f6c7755da351b8d02282dde1c190133c118a5ca9627b6fd87dfd5da
rtl8821aefw_wowlan.bin

ubuntu sha256
11e7ea00504fa2fa6f5216bb59403c4f2f20eec5b676c0add0695db3b0c4a335 rtl8821aefw_29.bin
025c13f2e7f7526e1f932049bed2146467318f547ffa8481804ecfd911cda695 rtl8821aefw.bin
df6fe0f14f6c7755da351b8d02282dde1c190133c118a5ca9627b6fd87dfd5da
rtl8821aefw_wowlan.bin

I'll post it to the bug report. It's difficult to do these comparisons, ubuntu
and leap don't play well together. So I have to install one, gather the
information. Then install the other, gather the information. Compare the saved
results.

[Carlos E.R.]

On 06/01/2019 22.31, Sidney_Kotic wrote:

...

> I'll post it to the bug report.  It's difficult to do these comparisons,
> ubuntu and leap don't play well together.  So I have to install one,
> gather the information.  Then install the other, gather the
> information.  Compare the saved results.

:-(

I think /I/ would be able to install Leap after Ubuntu, provided that
there is disk space.

Grub should be installed on each partition, not on the MBR. The MBR
should be "traditional". If using EFI, then no need to bother about
MBRs. I'm not familiar enough with Ubuntu to know how to do that.

--
Cheers, Carlos.

[Sidney_Kotic]

On 1/6/19 3:34 PM, Carlos E.R. wrote:

> I think /I/ would be able to install Leap after Ubuntu, provided that
> there is disk space.

Whelp...the life expectancy of ubuntu once I get the network up under leap can
be measured in jiffies.

> MBRs. I'm not familiar enough with Ubuntu to know how to do that.

From what I've seen so far it reminds me of Raspbian, and I have a Raspberry
working, sorta, right now that's telling me that "ls" is an illegal command when
I'm in a terminal. But it's playing mp3's started by a bash script in that same
window, the reason for it's existence is to play music 24X7, and running boinc
in the background. I like it better than the Android that my phone/kindle use.
All in all it's kinda like:
www.eviscerati.org/files/comics/hd/hd20180604.png