MX-18 RC1 Feedback

[Jerry3904]

I usually only get the hotel login page when I click on a browser page. Note that once connected you can right-click the NM icon in the Notification Area > Edit Connections.... There you can highlight the AP you are connected to, click the Edit button > Proxy tab.

[RichardTS]

Kindly pointing you to this as we cannot guess:

If posting hardware issues, please post the output of the terminal command "inxi -Fxrz" or use our "Quick-system-info" from the menu, at a minimum.

If posting nvidia-installer issues, please post the contents of /var/log/ddm.log.

If posting remaster issues, please include the contents of /var/log/live/live-remaster.log

If posting issues with MX-PackageInstaller "Popular Apps", please post contents of /var/log/mxpi.log or /var/log/mxpi.log.old (whichever contains the log of your issue).

inxi -Fxrz command result:

Code: Select all

System:    Host: mx1 Kernel: 4.19.0-1-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0 
           Desktop: Xfce 4.12.3 Distro: MX-18RC1_x64 Continuum December 17  2018 
           base: Debian GNU/Linux 9 (stretch) 
Machine:   Type: N/A System: LENOVO product: 81CU v: Lenovo YOGA 730-15IKB serial: <filter> 
           Mobo: LENOVO model: LNVNB161216 v: SDK0R32862 WIN serial: <filter> UEFI: LENOVO 
           v: 7KCN25WW(V1.06) date: 06/19/2018 
Battery:   ID-1: BAT1 charge: 53.8 Wh condition: 53.8/51.6 Wh (104%) 
           model: 43 65 6C 78 70 65 72 74 00 31 PABAS0241231 status: Full 
CPU:       Topology: Quad Core model: Intel Core i7-8550U bits: 64 type: MT MCP arch: Kaby Lake 
           rev: A L2 cache: 8192 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31872 
           Speed: 800 MHz min/max: 400/4000 MHz Core speeds (MHz): 1: 801 2: 800 3: 800 4: 800 
           5: 800 6: 800 7: 802 8: 800 
Graphics:  Device-1: Intel driver: i915 v: kernel bus ID: 00:02.0 
           Device-2: NVIDIA driver: nouveau v: kernel bus ID: 3b:00.0 
           Display: x11 server: X.Org 1.19.2 driver: modesetting,nouveau unloaded: fbdev,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (Kabylake GT2) v: 4.5 Mesa 18.2.6 
           direct render: Yes 
Audio:     Device-1: Intel driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           Sound Server: ALSA v: k4.19.0-1-amd64 
Network:   Device-1: Realtek driver: r8822be v: kernel port: 4000 bus ID: 3a:00.0 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 484.15 GiB used: 74.6 MiB (0.0%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLB512HAJQ-000L2 size: 476.94 GiB 
           ID-2: /dev/sda type: USB vendor: Patriot model: Memory size: 7.21 GiB 
Partition: ID-1: / size: 12.25 GiB used: 74.6 MiB (0.6%) fs: overlay dev: ERR-102 
Sensors:   System Temperatures: cpu: 45.0 C mobo: N/A gpu: nouveau temp: 511 C 
           Fan Speeds (RPM): N/A 
Repos:     Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http://la.mxrepo.com/antix/stretch stretch main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://ftp.us.debian.org/debian/ stretch-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://ftp.us.debian.org/debian/ stretch main contrib non-free
           2: deb http://security.debian.org/ stretch/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ stretch main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 221 Uptime: 34m Memory: 15.39 GiB used: 1.07 GiB (7.0%) Init: SysVinit 
           runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.25

[Jerry3904]

<Added as Mod the code tags to make more readable.>

[RichardTS]

Just checked, it's not there.

Just saw Adrian's post, so there's some hope perhaps.

Even on a 4.20 kernel (where it's still in staging) I'm unable to modinfo or modprobe a rt8822be or rtl8822be module, r8822be does work though

Code: Select all

kent@mx1:~
$ modinfo rt882be
modinfo: ERROR: Module rt882be not found.
kent@mx1:~
$ modinfo rtl882be
modinfo: ERROR: Module rtl882be not found.
kent@mx1:~
$ modinfo r8822be 
filename:       /lib/modules/4.20.0-042000rc6-lowlatency/kernel/drivers/staging/rtlwifi/r8822be.ko
description:    Realtek 802.11n PCI wireless core
license:        GPL
author:         Larry Finger	<Larry.FInger@lwfinger.net>
author:         Realtek WlanFAE	<wlanfae@realtek.com>
author:         lizhaoming	<chaoming_li@realsil.com.cn>
description:    PCI basic driver for rtlwifi
license:        GPL
author:         Larry Finger	<Larry.FInger@lwfinger.net>
author:         Realtek WlanFAE	<wlanfae@realtek.com>
author:         lizhaoming	<chaoming_li@realsil.com.cn>
firmware:       rtlwifi/rtl8822befw.bin
description:    Realtek 8822BE 802.11n PCI wireless
license:        GPL
author:         Larry Finger	<Larry.Finger@lwfinger.net>
author:         Realtek WlanFAE	<wlanfae@realtek.com>
description:    Realtek 802.11n PCI wireless core
license:        GPL
author:         Larry Finger	<Larry.FInger@lwfinger.net>
author:         Realtek WlanFAE	<wlanfae@realtek.com>
description:    Realtek 802.11n PCI wireless core
license:        GPL
author:         Larry Finger	<Larry.FInger@lwfinger.net>
author:         Realtek WlanFAE	<wlanfae@realtek.com>
srcversion:     75FBE534E42ABFB3D9F1570
alias:          pci:v000010ECd0000B822sv*sd*bc*sc*i*
depends:        mac80211,cfg80211
staging:        Y
intree:         Y
name:           r8822be
vermagic:       4.20.0-042000rc6-lowlatency SMP preempt mod_unload 
parm:           debug_level:int
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:           dma64:Set to 1 to use DMA 64 (default 0)
 (bool)
parm:           aspm:Set to 1 to enable ASPM (default 1)
 (int)
parm:           debug:Set debug level (0-5) (default 0)
parm:           debug_mask:Set debug mask (default 0) (ullong)
parm:           disable_watchdog:Set to 1 to disable the watchdog (default 0)
 (bool)
kent@mx1:~
$ sudo modprobe r8822be 
[sudo] password for kent: 
kent@mx1:~

When I modinfo r8822be I get the same result

I did also do a modprobe r8822be and it is working for right now.

Thanks guys! I really appreciate the help. I set the live USB up with both root and home persistence. Let's hope it stays. Screen resolution setting does not persist.

[RichardTS]

I usually only get the hotel login page when I click on a browser page. Note that once connected you can right-click the NM icon in the Notification Area > Edit Connections.... There you can highlight the AP you are connected to, click the Edit button > Proxy tab.

Maybe you are correct. I go back and forth from Windows all the time so sometimes I get confused. And I have been trying to make MX work for about 3 weeks so I don't remember what normally happens with an MX machine.

It seems to be working right now. Thanks for all the help!

[j2mcgreg]

I'm getting this in Chrome "Enter password to unlock your login keyring", which would be fine except there was no initial prompt to set up a password.

When you log-in the first time with your normal username and password, during the log-in process a new login-keyring is (shall be) generated automatically by "libpam-gnomekeyring", if not already existing. As protecting password used for this keyring the user's password is used. After login this keyring is automatically unlocked. You can check this by doing the following:
- close all programs like Chrome etc
- clear/remove all existing keyrings

Code: Select all

rm ~/.local/share/keyrings/*

- logout and login
- dont' start Chrome
- open Password and Keys from the Menu
and you'll find a unlocked login-keyring as indicated by the unlocked symbol:
Password-and-keys-login-keyring.png

When you now open Chromium or any other app requiring access to use the keyring,
you will/shall not see any prompt.

If this showing of a password-prompt for unlocking thy keyring happens again, we might have a timing issues during the log-in process.
In that case please do this:
First clear again as described above the keyring.
Next do open Settings -> Application Autostart and click to enable on "Secret Storage Service "GNOME-keyring"
This might fix the timing related issue, if not please report back here.

Thanks for this fehlix. Unfortunately life intervened and I had to put some things on hold. I'll try to get to it tonight and report back.

Unfortunately, it didn't work. I ran your code to remove all existing keyrings, then went to Passwords and Keys and there was no login-keyring visible unlocked or otherwise.

Also, under Settings, there is no entry for Application Autostart, so I couldn't try the second set of instructions.

Edit:

Mark this solved. It bothered me that the "Application Autostart" entry was missing so I reinstalled but this time I used a usb stick rather than a DVD. Since the MD5 sum for the DVD was correct, I wondered if the DVD drive on this old computer was faulty. Also, this time I waited for all the updates to be installed and then I rebooted. Only then did I install Chromium and launch it. No prompts for a password occurred.

[derrotmax]

The computer is a Lenovo YOGA 730-15ikb. Intel Core i7-8550U, both Intel and nVidia graphics, 16 GB ram, 4K display.

No flavor of MX-17 will run correctly on it. None of the monthlys. The wireless (rtl8822be) simply does not work.

Richard, I had the same problem as you with my brand new Lenovo Y7000P-1060 (i7-8750H, Nvidia 1060, and the same wireless card) -- in my case the problem is the ideapad_laptop kernel module -- if it's enabled, the wireless won't be seen at all, even though it works just fine in Windows (which also explains why the same problem is seen in other distros). Running a simple:

Code: Select all

sudo modprobe -r ideapad_laptop

allowed the wireless to show up correctly, so I just added a blacklist to modprobe.d for the ideapad_laptop module and it's been smooth sailing since.

[RichardTS]

The computer is a Lenovo YOGA 730-15ikb. Intel Core i7-8550U, both Intel and nVidia graphics, 16 GB ram, 4K display.

No flavor of MX-17 will run correctly on it. None of the monthlys. The wireless (rtl8822be) simply does not work.

Richard, I had the same problem as you with my brand new Lenovo Y7000P-1060 (i7-8750H, Nvidia 1060, and the same wireless card) -- in my case the problem is the ideapad_laptop kernel module -- if it's enabled, the wireless won't be seen at all, even though it works just fine in Windows (which also explains why the same problem is seen in other distros). Running a simple:

Code: Select all

sudo modprobe -r ideapad_laptop

allowed the wireless to show up correctly, so I just added a blacklist to modprobe.d for the ideapad_laptop module and it's been smooth sailing since.

Very interesting! Earlier with MX-17 I was getting things called ideapad_laptop this and ideapad_laptop that. Particularly when running rfkill.

I am going to try your suggestion. Did you stumble on this or was it an educated guess?

[derrotmax]

Very interesting! Earlier with MX-17 I was getting things called ideapad_laptop this and ideapad_laptop that. Particularly when running rfkill.

I am going to try your suggestion. Did you stumble on this or was it an educated guess?

An educated guess got me going in the right direction. I looked at the rfkill list too (which is where I initially saw the ideapad_laptop entries), and no matter what, my realtek adapter was hardblocked and would never enter an enabled state, even when running rfkill unblock. I then swapped the Realtek card out for an Intel one that ran fine in another MX laptop, but the behavior was the exact same -- at that point I knew that I should be looking for a kernel-level solution (especially since Windows had no issue) -- adding the "ideapad_laptop" module and "disabled wireless" to that search returned all sorts of people that are seeing the same issue regardless of Linux distro. Disabling the ideapad_laptop module and eventually blacklisting it allows the Realtek adapter to start up properly and work without issue.

[Jerry3904]

I am going to lock this thread, since Final is out and these comments need to be seen against a current version.

Thanks to everybody for the input!