LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   4MLinux (https://www.linuxquestions.org/questions/4mlinux-115/)
-   -   The 4MLinux 35 series. (https://www.linuxquestions.org/questions/4mlinux-115/the-4mlinux-35-series-4175682805/)

Edward4m 01-31-2021 11:30 AM

Quote:

Originally Posted by zk1234 (Post 6214198)
Hi,

In your first post: you were able to install 35.0 and upgrade to 35.1. The 35.1 system boots to JWM, but it hangs.
In your second post: unable to boot, kernel panic.

These are two totally different scenarios. Which of them is correct? If the second one, then try to set Secure Boot to disabled in your BIOS. If this does not help, then additionally set Legacy Support to enabled. You should find these two options in the advanced BIOS settings.

.

Well, both happened, actually.
Still no succes, also unchecked 'enable ms uefi ca key'
The only option I have is 'legacy support enabled and secure boot disabled'
If I choose 'legacy support disabled and secure boot enabled' or both disabled, things go wrong in the bios.
I then get a message 'start PXE over ipv6' in other words it wants to start from network.
Back to factory settings helped.
But now I read a Bash message during boot, after an eufi install.
-bash: error while loading shared libraries: /lib/libncurses.so.6: file too short
This may be use full.
Always grateful for what you do,
Edward

zk1234 01-31-2021 12:11 PM

Hi,

Sorry, but now I understand nothing. If you tried 'legacy support enabled and secure boot disabled' then this was not UEFI install meaning that 4MLinux should use LILO. Was that so? Could you see LILO during the boot?

If you did not see LILO, then set 'legacy support enabled and secure boot disabled' and perform fresh installation.

PS.
"loading shared libraries: /lib/libncurses.so.6: file too short" means read-write errors on your disk.

Edward4m 02-02-2021 11:07 PM

Quote:

Originally Posted by zk1234 (Post 6214340)
Hi,

Sorry, but now I understand nothing. If you tried 'legacy support enabled and secure boot disabled' then this was not UEFI install meaning that 4MLinux should use LILO. Was that so? Could you see LILO during the boot?

If you did not see LILO, then set 'legacy support enabled and secure boot disabled' and perform fresh installation.

PS.
"loading shared libraries: /lib/libncurses.so.6: file too short" means read-write errors on your disk.

Hi, sorry for this rather late reply.

I do not understand it neither. I have performed a fresh usb 35.1 install, following your instructions, and the result remains the same.
Weither this is a uefi or a legacy install with LILO.

In order to find out that it is not my shortcomings (I do have them, I admit), I did a upup bionicpup 32-8.0 install and with succes.

I still have a good working 35.0 on my other older HP laptop, but I am a bit reluctant to update.

Sorry for the inconvenience.

Kind regards, Edward

zk1234 02-04-2021 03:32 PM

Quote:

Originally Posted by Edward4m (Post 6215395)
Hi, sorry for this rather late reply.

I do not understand it neither. I have performed a fresh usb 35.1 install, following your instructions, and the result remains the same.
Weither this is a uefi or a legacy install with LILO.

In order to find out that it is not my shortcomings (I do have them, I admit), I did a upup bionicpup 32-8.0 install and with succes.

I still have a good working 35.0 on my other older HP laptop, but I am a bit reluctant to update.

Sorry for the inconvenience.

Kind regards, Edward

Hi,

Keeping my fingers crossed for successful updates ;-)

Kind regards,
zk1234

.

Edward4m 02-05-2021 01:39 PM

Quote:

Originally Posted by zk1234 (Post 6216185)
Hi,

Keeping my fingers crossed for successful updates ;-)

Kind regards,
zk1234

.

Hello,

No problems updating on the good old HP 6730b.

Have a great weekend,
Edward

linustalman 02-06-2021 01:57 AM

I wish DW wasn't so slow with updating their pages. They still don't have v35 on https://distrowatch.com/dwres.php?re...distro=4mlinux. I'd like to leave a review but can't. I messaged them weeks ago but to no avail.

linustalman 02-07-2021 04:00 AM

1 Attachment(s)
They omit many versions along the way also. That's bad form!

linustalman 02-14-2021 01:01 AM

DW still shows v34 as the latest on the review page. 😞

linustalman 02-21-2021 01:52 AM

Still no update on DW - oh dear!

I'm currently on v35.1 and want to vote and leave a review but cannot as things stand.

zk1234 02-21-2021 04:29 PM

4MLinux 35.2 released.
 
This is a minor (point) release in the 4MLinux STABLE channel, which comes with the Linux kernel 5.4.91. The 4MLinux Server now includes Apache 2.4.46, MariaDB 10.5.8, and PHP 7.4.14.
You can update your 4MLinux by executing the "zk update" command in your terminal (fully automatic process).

More:
https://4mlinux-releases.blogspot.co...-released.html

.

linustalman 02-27-2021 02:25 AM

Quote:

Originally Posted by zk1234 (Post 6222951)
This is a minor (point) release in the 4MLinux STABLE channel, which comes with the Linux kernel 5.4.91. The 4MLinux Server now includes Apache 2.4.46, MariaDB 10.5.8, and PHP 7.4.14.
You can update your 4MLinux by executing the "zk update" command in your terminal (fully automatic process).

More:
https://4mlinux-releases.blogspot.co...-released.html

.

Updated to 35.2 in my AQEMU VM - no issues (apart from having to reset my resolution but that was simple to fix). :)

linustalman 03-07-2021 07:34 AM

Hi Zbigniew.

I'm using 4MLinux 35.2 in virt-manager (I copied the old .img file from my AQEMU folder). On each bootup, the Wbar is off. How can I have it enabled on every log in?

I wonder if it's anything to do with the full screen resolution?

Thanks.

zk1234 03-07-2021 11:32 AM

Quote:

Originally Posted by linustalman (Post 6228137)
Hi Zbigniew.

I'm using 4MLinux 35.2 in virt-manager (I copied the old .img file from my AQEMU folder). On each bootup, the Wbar is off. How can I have it enabled on every log in?

I wonder if it's anything to do with the full screen resolution?

Thanks.

Let's start with reinstalling the jwm package. You'll find it in the /var/4MLinux directory.

.

linustalman 03-07-2021 01:30 PM

Quote:

Originally Posted by zk1234 (Post 6228194)
Let's start with reinstalling the jwm package. You'll find it in the /var/4MLinux directory.

.

Perfect! I went to that folder and ran:
Code:

zx addon_jwm-2.3.7.tar.xz
I did a reboot and had to re-set my resolution back to 1920*1080 from 1024*768. All good now. :)

linustalman 03-13-2021 12:17 PM

1 Attachment(s)
DW finally updated it!


All times are GMT -5. The time now is 11:34 AM.