MX-18 RC1 Feedback

[Eadwine Rose]

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).

[Jerry3904]

I see a recent Torvalds item in GitHub:

https://github.com/torvalds/linux/tree/ ... /rtl8822be

Looks like it was merged into the kernel 4.18. Have you tried to modprobe it on MX-18rc1?

[Jerry3904]

Just checked, it's not there.

[Adrian]

It's in "staging" I don't think those are enabled by default, it might require a kernel recompile

[Jerry3904]

Just checked, it's not there.

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

[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.

[gsm]

MX Linux is a very nice distribution. I use MX17 32-bit on a HP Mini netbook.
All other distributions, i tried are slower than MX Linux and some have windows that are to big for a 1024x600 display.

I have installed the latest MX Linux beta 64-bit on a HP m8000 (m8189.nl-a).
Everything running fine.

I have however two remarks:

1) In the Netherlands the Dutch keyboard is hardly used. Almost everybody has a United States Intl 105 key board, often with the Euro sign at key 5.
Under Windows one can type the Euro sign by pressing Ctrl + Alt + 5.
So during installation it would be better, when Dutch language is choosen, to default to a US keyboard, instead of a NL keyboard.
This is also the case with Ubuntu and Mint, i believe.

2) It would be fine if it were possible to install Grub MBR at a disk where the /boot partition is.
I have /root on a SSD drive and would like to have /boot and /Home at another drive, booting from the MBR on this other drive.
With Ubuntu, Mint, Manjaro, Deepin etc this is possible
MX Linux can only install Grub at the disk, where the /root partition is.
In my case this is the SSD, where the Windows boot loader is on. So i cannot install Grub to MBR, without overwriting the Windows 10 boot loader.
The only bypass i have is to install grub at /root, instead of MBR.
I can than use Manjaro Grub to find and run MX Linux.

[anticapitalista]

1. Do other Dutch users agree? If so, easy to change
2. You also have the option to not install grub at all.

[kmathern]

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:~

[Adrian]

MX Linux can only install Grub at the disk, where the /root partition is.

I don't think there's true, you can select the drive from "System boot disk" dropdown menu. I just tried and was able to install on a sdb disk with I used for /boot while / was on sda.

Actually the opposite was true I was not able to install on sda MBR but maybe it was because I use GPT

Code: Select all

"grub-install --target=i386-pc --recheck --no-floppy --force --boot-directory=/mnt/antiX/boot /dev/sda"
Installing for i386-pc platform.
grub-install: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible.
grub-install: error: embedding is not possible, but this is required for cross-disk install.