MX-18 RC1 Feedback

[fehlix]

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. 

@Adrin, you can install BIOS/i386-pc Grub onto GPT disk. I usually install both UEFI and BIOS Grub's,
so I can boot in either mode using the identical grub.cfg.
To enable a GPT partition to accept MBR-grub-installs, I do this:
- shrink existing ESP/EFI-partition by about 5MB
- create a new "unformated" partition within that 5MB empty space
- mark the unformated partition as "bios-grub" (or "grub-bios" ?)
And now you can install with the above commmand grub-i386 onto this GPT partition.
And next time you boot in BIOS/MBR bios will boot into grub-i386, using the same grub.cfg as in UEFI-mode.

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

I will post the results of terminal command "inxi -Fxrz" later. At work right now and booted up in Windows...

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

Yes it works. Just not on public networks needing a login. I will also check it when I return to my home this weekend. Should work just fine there unless it doesn't give me the login screen...

[Adrian]

@Adrin, you can install BIOS/i386-pc Grub onto GPT disk. I usually install both UEFI and BIOS Grub's,

Are you sure it works on 2 disks, see the "is required for cross-disk install" message

Code: Select all

grub-install: error: embedding is not possible, but this is required for cross-disk install.

[fehlix]

@Adrin, you can install BIOS/i386-pc Grub onto GPT disk. I usually install both UEFI and BIOS Grub's,

Are you sure it works on 2 disks, see the "is required for cross-disk install" message

Code: Select all

grub-install: error: embedding is not possible, but this is required for cross-disk install.

My note, was only a comment about installing BIOS-grub onto GPT disk - nothing more ...

[Adrian]

I don't have a problem installing BIOS GRUB on GPT disk in general the problem is when installing on two disks with separate /boot.

[fehlix]

I don't have a problem installing BIOS GRUB on GPT disk in general the problem is when installing on two disks with separate /boot.

Ah, ok I see.
There are two: ways of having Grub-installed into the MBR: embedded or not-embedded.
In the embedded case: The full grub core.img is placed into the post-MBR gab before partition-table-fs block.
in this case grub is fine with finding the grub.cfg and related modules from another disk by using it's filesystem modules.
In the non-embedded case where embedding into MBR-gap is not possible, grub cannot yet see the filesystem, but requires
BIOS-alike block-jumps to the core.img saved into a fixed block of the disk. Those jumps
are made with help of BIOS-function calls and are only possible within the same disk.
HTH

[Fornhamfred]

Not sure if anyone has reported this but on new install I moved the deskbar to the bottom of the screen and then configured another panel to be vertical and never hide but it still hides.

[kmathern]

Yes it works. Just not on public networks needing a login. I will also check it when I return to my home this weekend. Should work just fine there unless it doesn't give me the login screen...

I can load (modprobe) the r8822be module but I don't have the hardware so don't know if it actually works or not.

Have you seen or tried this: https://ubuntuforums.org/showthread.php ... st13748726 ?

[RichardTS]

Yes it works. Just not on public networks needing a login. I will also check it when I return to my home this weekend. Should work just fine there unless it doesn't give me the login screen...

I can load (modprobe) the r8822be module but I don't have the hardware so don't know if it actually works or not.

Have you seen or tried this: https://ubuntuforums.org/showthread.php ... st13748726 ?

I followed the Ubuntu link. r8822be.conf created with the option inserted. Then the conf file generates a parse error when I modprobe r8822be. Deleting r8822be.conf makes modprobe work.

Then the first time I tried to connect it went round and round and then said “network disconnected” in the upper right corner. Never got a login screen. So I tried again. This time it connected. Still never gave me the hotel login page.