4MLinuxThis forum is for the discussion of 4MLinux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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
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.
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.
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 ;-)
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.
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).
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).
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?
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.