MX Linux Forum

Posted: **Mon Jul 17, 2023 8:29 am**

@OlafD To get a Transifex account: viewtopic.php?t=38671

Posted: **Mon Jul 17, 2023 9:34 am**

8bit wrote: Sun Jul 16, 2023 2:13 pm
doodstecsonhere wrote: Sun Jul 16, 2023 1:08 pm
thinkpadx wrote: Sat Jul 15, 2023 12:17 pm did not want to bug and PM someone about this dumb question. but if rc1 installed great and boots up on 2 laptops, and I DID upgrade both today; then i am good - yes? or NO? i should just not worry about it.i should be able to upgrade to final release when it happens...

sorry to waste a developers time on this. Have a good one!
I read the official blog posts from MX website of the RC2 and RC2 releases of MX 23. It was mentioned that updating the RC releases to final release is fully supported. Looks like you're all set to receive the final release when it comes automatically via updates.
With the exception that any apps added after R1, R2 will not be included in the upgrade. A small thing, but worth pointing out.

Oh, I missed that one. Thanks!

Posted: **Mon Jul 17, 2023 11:29 am**

First, thanks for the wonderful work you're doing at MX.
Problem with installer on MX23-RC2-XFCE
Live USB created with MX19 utility.
Computer: Circa 2010 Athlon II Notebook, BIOS only, no UEFI.
Installer updated to 23.7.08mx23.
When installing on GPT partitioned drive, installer seems unable to format and copy BIOS-GRUB partition. Prints message: "Failed to format partition"
Same problem occurs on similar installation in VirtualBox.
Installs OK with MBR partioning.
QuickInfo and minstall.log contents follow.

inxi.txt

minstall.log

Posted: **Mon Jul 17, 2023 1:42 pm**

8bit wrote: Sun Jul 16, 2023 2:13 pm
doodstecsonhere wrote: Sun Jul 16, 2023 1:08 pm... the official blog posts from MX website of the RC2 and RC2 releases of MX 23... mentioned ... updating ... to final release is fully supported. ... automatically via updates.
With the exception that any apps added after R1, R2 will not be included in the upgrade. A small thing, but worth pointing out.

Would using xdelta help with this? (And would there be any better method(s)?)

Posted: **Mon Jul 17, 2023 3:43 pm**

pmarcot wrote: Mon Jul 17, 2023 11:29 am First, thanks for the wonderful work you're doing at MX.
Problem with installer on MX23-RC2-XFCE
Live USB created with MX19 utility.
Computer: Circa 2010 Athlon II Notebook, BIOS only, no UEFI.
Installer updated to 23.7.08mx23.
When installing on GPT partitioned drive, installer seems unable to format and copy BIOS-GRUB partition. Prints message: "Failed to format partition"
Same problem occurs on similar installation in VirtualBox.
Installs OK with MBR partioning.

Thanks for the report. The issue is identified.
The reason is simply when "wiping" the bios_grub partition the tool "dd" is used to fill-up the partition until it is full,
but at the some time dd returns an error code "No space left on device". Which was intended but the error code was not captured. So the installation "failed".
Workaround until a fixed version comes along:
Do create a bios_grub partition with Gparted with
max size 1MB
and format as "unformatted" or as "cleared"
and set the mark/flag of this partition as "bios_grub".
and within the installer do not select BIOS_GRUB.
The existing bios-grub partition will be used anyway when grub-install is invoked to write it's GRUB core-image to the "MBR" on a GPT disk.
Thanks

Posted: **Mon Jul 17, 2023 4:28 pm**

fehlix wrote: Mon Jul 17, 2023 3:43 pm
pmarcot wrote: Mon Jul 17, 2023 11:29 am First, thanks for the wonderful work you're doing at MX.
Problem with installer on MX23-RC2-XFCE
Live USB created with MX19 utility.
Computer: Circa 2010 Athlon II Notebook, BIOS only, no UEFI.
Installer updated to 23.7.08mx23.
When installing on GPT partitioned drive, installer seems unable to format and copy BIOS-GRUB partition. Prints message: "Failed to format partition"
Same problem occurs on similar installation in VirtualBox.
Installs OK with MBR partioning.
Thanks for the report. The issue is identified.
The reason is simply when "wiping" the bios_grub partition the tool "dd" is used to fill-up the partition until it is full,
but at the some time dd returns an error code "No space left on device". Which was intended but the error code was not captured. So the installation "failed".
Workaround until a fixed version comes along:
Do create a bios_grub partition with Gparted with
max size 1MB
and format as "unformatted" or as "cleared"
and set the mark/flag of this partition as "bios_grub".
and within the installer do not select BIOS_GRUB.
The existing bios-grub partition will be used anyway when grub-install is invoked to write it's GRUB core-image to the "MBR" on a GPT disk.
Thanks

Your solution is cristal clear and worked like a charm. Thanks so much.
Long live MXLinux

Posted: **Mon Jul 17, 2023 5:07 pm**

yes i am stunned at fehlix's response! wow! nailed it...

Posted: **Tue Jul 18, 2023 8:10 am**

I'm not sure if this is an RC2 bug or if it was present in MX21.

I loaded up RC2 via a live USB using `p_static_root` with persistence.

The computer is an HP EliteBook x360 1040 G6. It has an Intel Wi-Fi 6 AX200, which didn't have a driver detected on boot up.

Code: Select all

Device-2: Intel Wi-Fi 6 AX200 driver: N/A

Code: Select all

*-network UNCLAIMED
       description: Network controller
       product: Wi-Fi 6 AX200
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:6d:00.0
       version: 1a
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix cap_list
       configuration: latency=0
       resources: memory:e0200000-e0203fff

I looked in the dmesg output for any errors and found this

Code: Select all

[   18.154287] iwlwifi: probe of 0000:6d:00.0 failed with error -110

I searched for the driver using this site https://itslinuxfoss.com/install-intel- ... 00-driver/, and https://www.intel.com/content/www/us/en ... eless.html found the correct driver, and copied it into `/lib/firmware`. However, upon reboot, the device still didn't detect the driver. The driver is `iwlwifi-cc-46.3cfab8da.0.tgz`, which could be added at some point. Is there anything else I should be doing besides copying it over to `/lib/firmware` for the live USB with persistence?

Thanks!

Posted: **Tue Jul 18, 2023 9:48 am**

uidmap package is missing from MX Linux RC2. It's needed in order to run distrobox/podman. It's installed by default on Debian 12, so it's not set as a dependency for the distrobox package when it's installed. When you try and create a image using distrobox you get an error that newuidmap is missing.

Posted: **Tue Jul 18, 2023 11:15 am**

Danathar wrote: Tue Jul 18, 2023 9:48 am uidmap package is missing from MX Linux RC2. It's needed in order to run distrobox/podman. It's installed by default on Debian 12, so it's not set as a dependency for the distrobox package when it's installed. When you try and create a image using distrobox you get an error that newuidmap is missing.

i suggest this is a fault of the debian packaging. please file the pug against debian's package.

MX Linux Forum

MX-23 RC2 (Xfce) feedback thread

Re: MX-23 RC2 (Xfce) feedback thread

Re: MX-23 RC2 (Xfce) feedback thread

Re: MX-23 RC2 (Xfce) feedback thread

Re: MX-23 RC2 (Xfce) feedback thread

Re: MX-23 RC2 (Xfce) feedback thread

Re: MX-23 RC2 (Xfce) feedback thread

Re: MX-23 RC2 (Xfce) feedback thread

Re: MX-23 RC2 (Xfce) feedback thread

Re: MX-23 RC2 (Xfce) feedback thread

Re: MX-23 RC2 (Xfce) feedback thread