Puppy Linux Discussion Forum

Read all about it here:

https://bkhome.org/news/202207/easyos-d ... eased.html

And the project snapshots here:

https://bkhome.org/news/202207/oe-and-w ... y-423.html

Continuing to fix little buglets after the major architectural change with 4.2.
Looking pretty good.

I posted a to-do list somewhere, oh yes, here:

https://forum.puppylinux.com/viewtopic. ... 553#p60553

...want to get back onto some of those, plus a couple not listed.

Feedback welcome!

Bonjour à vous M. Kauler;

Transition from version 4.2.2 to 4.2.3 without problem. The update was made via the Update icon. Very appreciate your work!

Voilà!

Sorry, but i can't seem to find the new EasyApps pet, the last one at http://distro.ibiblio.org/easyos/noarch ... es-noarch/ is 3.1.2.2, or am i looking at the wrong place (or too early and you haven't time to upload it yet)?

scsijon wrote: ↑Mon Jul 04, 2022 11:25 pm

Sorry, but i can't seem to find the new EasyApps pet, the last one at http://distro.ibiblio.org/easyos/noarch ... es-noarch/ is 3.1.2.2, or am i looking at the wrong place (or too early and you haven't time to upload it yet)?

Uploaded it just now.

On booting EasyOS 4.2.3, I am sometimes seeing a strange message.

Deferred saving last session please wait..

This message has only been displayed following a boot / reboot, when 'Do Not Save' is selected when shutting down or rebooting the previous session. I have done several shutdowns /reboots to check. The message is only being intermittently displayed. It appears just following entering the decryption password.

TerryH wrote: ↑Wed Jul 06, 2022 12:23 am

On booting EasyOS 4.2.3, I am sometimes seeing a strange message.

Deferred saving last session please wait..

This message has only been displayed following a boot / reboot, when 'Do Not Save' is selected when shutting down or rebooting the previous session. I have done several shutdowns /reboots to check. The message is only being intermittently displayed. It appears just following entering the decryption password.

That would happen if you saved via the "save" icon on the desktop, then at shutdown chose not to save.
It will still save what you earlier saved, but it is deferred until the next bootup.

Hi,

Booted 4.2.3 from a fresh install. Got:

WARNING; MISSING FIRMWARE
The Linux kernel reports this firmware is missing:
 usb 1-2.4: Direct firmware load for ar3k/
 AthrBT_0x31010000.dfu failed with error -2
 
 Please write the name of the firmware.You will have 
 to search the internet to find it.
 Note, the above information has also been logged 
 to /tmp/report-fw-fail.log

Booting from SSD nvme drive (interna hard disk). Takes times for finding driver etc.

Is there a way to increase global font size beyond 138?

While working with live usb, save session is not working. It shows saving, however nothing saved. keyboard entry is only come into effective after few minutes after every reboot.

I did a fresh install of 4.2 on a 240GB SSD in an external case/USB3. This did a upgrade with new scripts via the updater's delta, to 4.2.3 without issue. Have gotten a couple of momentary black screens with old acer 4:3 LCD, & my Mele PCG35 BLK J4125 only has internal Intel600 GPU

The internal m.2 SSD nvme has Easy4.1. Manual (attempted) upgrade to 4.2 borks boot ..as does 4.2.3
An example for hdd from "Limine will not boot on Dell D630 #189" at github:
KERNEL_PATH=hdd://1:8/easyos-4.2.2/vmlinuz
MODULE_PATH=hdd://1:8/easyos-4.2.2/initrd
If the 1:8 refers to partitions found in /dev/block/ the nvme shows up as 259:0 259:1 etc. Which I believe threw boot error *Partition number outside 0-256 range*
Example for hdd (continued) had Limine config's last line as
KERNEL_CMDLINE=initrd=initrd rw wkg_dev=sda8 wkg_dir=easyos-4.2.2/
That's a bit different to all the experiments I did, with inc. the 2nd partition's UUID, so I have a few more to try
I see Limine has a community discord, so plenty of support
(I basically had the run-of-the-mill *couldn't find volume in config file*/*couldn't meaningfully match vol with path in config* sort of Limine panic thing)

That "1:8" is the drive-number:partition-number
Both are 1-based, that is, start from 1.
drive-number 1 is the first drive that the computer recognizes.

I see. There's the onboard/built-in mmcblk0 drive, then there's the nvme0n1 m.2 SSD. So the main partition at 2:2 might be worth a try (before the last 2:3 SWAP partition). There's no 2.5" SATA SSD fitted, then anything plugged into USB, would be sda/drive 3
I like to think the momentary black screens have gone, with this short usage has been 99.9% good (happened twice)
This Mele J4125 model has never had audio work from the JACK port with any linux distro, & I happened to have a HDMI to VGA adaptor that does have a JACK port, which I only use for audio (or plumb in a TV with HDMI)
HDMI takes priority over native VGA at boot, so at times, I may boot without a screen, knowing to tap away at bootkey (F7 for Mele), then down the drive list 4-6 times to select something ..if correct, the monitor will come alive with the desktop
This current SSD in an external case, often wouldn't populate in the boot list, & powering PC off & back on would bring it up

my lamine cfg in SDD (HP Laptop) as given below:-

QUIET=yes
TIMEOUT=0
GRAPHICS=no
DEFAULT_ENTRY=1
EDITOR_ENABLED=no
INTERFACE_BRANDING=EasyOS Limine Boot Manager

:EasyOS dunfell
COMMENT=EasyOS Dunfell bootup
PROTOCOL=linux
TEXTMODE=yes
KERNEL_PATH=boot://6/easyos/vmlinuz
MODULE_PATH=boot://6/easyos/initrd
KERNEL_CMDLINE=initrd=initrd rw wkg_uuid=7eef90f7-8243-42cb-98ea-f6736db46568 wkg_dir=easyos/

Boot failure as under

finding drives...............mount: can't resd '/etc/fstab' : no suh file or directory

easyos folder having 3 files. Still, reporting easy.sfs not found.

Ramachandra Iyer wrote: ↑Thu Jul 07, 2022 2:35 am

KERNEL_CMDLINE=initrd=initrd rw wkg_uuid=7eef90f7-8243-42cb-98ea-f6736db46568 wkg_dir=easyos/

Boot failure as under

finding drives...............mount: can't resd '/etc/fstab' : no suh file or directory

easyos folder having 3 files. Still, reporting easy.sfs not found.

can you run blkid and paste the output?

blkid
/dev/nvme0n1p8: LABEL="mabox22" UUID="d9bb49e4-6dbc-4839-a255-d7e8021751c5" TYPE="ext4"
/dev/nvme0n1p7: LABEL="rootantiX21" UUID="8f553b5c-05b2-4159-a93e-bb7df1c13b69" TYPE="ext4"
/dev/nvme0n1p6: LABEL="200322a" UUID="8f0dc1a3-ef22-48b1-97d7-80cf42195846" TYPE="ext4"
/dev/nvme0n1p5: LABEL="EASY" UUID="F5B3-01B1" TYPE="vfat"
/dev/nvme0n1p4: UUID="B632EF6032EF2459" TYPE="ntfs"
/dev/nvme0n1p3: LABEL="Windows" UUID="0C448DF6448DE336" TYPE="ntfs"
/dev/nvme0n1p2: TYPE="vfat"
/dev/nvme0n1p1: LABEL="SYSTEM" UUID="5AB8-882D" TYPE="vfat"
/dev/sda2: LABEL="easy2" UUID="2c381e00-fae4-11ec-8b19-5d8917d6d563" TYPE="ext4"
/dev/sda1: UUID="2EDC-7A9D" TYPE="vfat"
/dev/zram1: LABEL="TOPLEVELZRAM" UUID="0d4c20bc-e955-4b7e-a761-079007ea8d55" TYPE="ext2"
/dev/loop0: TYPE="squashfs"

KERNEL_PATH=boot://6/easyos/vmlinuz
MODULE_PATH=boot://6/easyos/initrd

the 6 indicates you are booting an easy install on
/dev/nvme0n1p6: LABEL="200322a" UUID="8f0dc1a3-ef22-48b1-97d7-80cf42195846" TYPE="ext4"
but

KERNEL_CMDLINE=initrd=initrd rw wkg_uuid=7eef90f7-8243-42cb-98ea-f6736db46568 wkg_dir=easyos/

seems to be a working partiton on a different disk?

williwaw wrote: ↑Thu Jul 07, 2022 6:51 am

KERNEL_CMDLINE=initrd=initrd rw wkg_uuid=7eef90f7-8243-42cb-98ea-f6736db46568 wkg_dir=easyos/

The above is part uuid of partition /dev/nvme0n1p6. Both are on same partition. nvme0n1p6

Ramachandra Iyer wrote: ↑Thu Jul 07, 2022 7:50 am

williwaw wrote: ↑Thu Jul 07, 2022 6:51 am

KERNEL_CMDLINE=initrd=initrd rw wkg_uuid=7eef90f7-8243-42cb-98ea-f6736db46568 wkg_dir=easyos/

The above is part uuid of partition /dev/nvme0n1p6. Both are on same partition. nvme0n1p6

wkg_uuid needs to be the filesystem UUID, as returned by blkid utility, not the PARTUUID.

Greetings to all!

Just a quick feedback:

Last week I've tested EasyOS 4.2.2 Dunfell release on my Hybrid-Graphics notebook, which by default has some kernel issues in dmesg described here:

viewtopic.php?p=60644#p60644

After a default boot of EasyOS when the desktop appeared, I've successfully configured Keyboard language settings, restarted X and then opened sakura terminal and checked dmesg and I've not found any errors in dmesg.

So I would like to ask, is it maybe because of the init of EasyOS, or is it because a kernel feature?
I've many times compiled huge kernels with Puppy Linux Woof-CE kernel-kit, and none of those are error free in dmesg with this Hybrid-Graphics notebook.
And if X restart failed in EasyOS 4.2.2 then I ran xorgwizard and that is successfully recognised I have Dual Graphics, so then I've choose nouveau and after that xwin, And then X started again.

I would like to say thanks for Dual-Graphics support in EasyOS also!

In the near future I plan to test 4.2.3 too!

Update to this post:

I've wrote the 4.2.3 amd64 Dunfell img clearly to the destination pendrive, and the experiences are the same positive:

I have no dmesg errors,
the differences with this test now is that I ran xorgwizard, selected nouveau, again after nouveau, widescreen 1920x1080, then asked me to reboot, OK, then started again with no issues.

xorgwizard in EasyOS is almost a complete rewrite, completely different from the xorgwizard script in the pups.

It has been a work-in-progress for a very long time, and every now and again I hack on it.

Anyway, glad you like it.

After a default boot of EasyOS when the desktop appeared, I've successfully configured Keyboard language settings, restarted X and then opened sakura terminal and checked dmesg and I've not found any errors in dmesg.

So I would like to ask, is it maybe because of the init of EasyOS, or is it because a kernel feature?
I've many times compiled huge kernels with Puppy Linux Woof-CE kernel-kit, and none of those are error free in dmesg with this Hybrid-Graphics notebook.

I don't know. We also receive feedback with the opposite experience, that the computer works flawlessly on some other Linux or pup, but has problems with EasyOS.

There must be something in the kernel config that your computer likes!

BarryK wrote: ↑Thu Jul 07, 2022 10:17 am

Ramachandra Iyer wrote: ↑Thu Jul 07, 2022 7:50 am

williwaw wrote: ↑Thu Jul 07, 2022 6:51 am

KERNEL_CMDLINE=initrd=initrd rw wkg_uuid=7eef90f7-8243-42cb-98ea-f6736db46568 wkg_dir=easyos/

The above is part uuid of partition /dev/nvme0n1p6. Both are on same partition. nvme0n1p6

wkg_uuid needs to be the filesystem UUID, as returned by blkid utility, not the PARTUUID.

I have replaced UUID of /dev/nvme0n1p6. Still not booting. Getting message that Can't mount etc/fstab and not able to find easy.sfs. Issues in boot process?.

Ramachandra Iyer wrote: ↑Thu Jul 07, 2022 1:32 pm

BarryK wrote: ↑Thu Jul 07, 2022 10:17 am

Ramachandra Iyer wrote: ↑Thu Jul 07, 2022 7:50 am

The above is part uuid of partition /dev/nvme0n1p6. Both are on same partition. nvme0n1p6

wkg_uuid needs to be the filesystem UUID, as returned by blkid utility, not the PARTUUID.

I have replaced UUID of /dev/nvme0n1p6. Still not booting. Getting message that Can't mount etc/fstab and not able to find easy.sfs. Issues in boot process?.

Note, you can use "wkg_dev=nvme0n1p6" instead of wkg_uuid

It seems that the internal drive is not being recognized in the initrd.
Isn't this the same problem that you have been having for a very long time?

You will probably see twenty dots after "Finding drives", which means that it is in a loop, every second running blkid to find the drive, and failing. Then after 20 seconds times out.

This is a fundamental hardware problem in your computer. I do not know what kernel configuration, or kernel module, or firmware, will enable the drive to be recognized.

[/quote]

It seems that the internal drive is not being recognized in the initrd.
Isn't this the same problem that you have been having for a very long time?

You will probably see twenty dots after "Finding drives", which means that it is in a loop, every second running blkid to find the drive, and failing. Then after 20 seconds times out.

This is a fundamental hardware problem in your computer. I do not know what kernel configuration, or kernel module, or firmware, will enable the drive to be recognized.
[/quote]

Sir, Same issue. However, there is some progress while compared to previous boot process.

Note, you can use "wkg_dev=nvme0n1p6" instead of wkg_uuid

As suggested by you, I have replaced wkg-uuid with wkg-de=nvme0nlp6. No such delay in finding drivers....... quick response. My error report image is given below:

Thanks for your reply BarryK!

I don't know. We also receive feedback with the opposite experience, that the computer works flawlessly on some other Linux or pup, but has problems with EasyOS.

There must be something in the kernel config that your computer likes!

I've tested this notebook with MX Linux AHS live iso also, but it has the same errors in dmesg that is why I tried to guess it may be the init. Howewer it can may be kernel configuration too. I try to give feedback later times again, in hope of finding solution to this problem in pups too!

Aam - can I ask you to give me dotconfig of the EasyOS kernel somehow? If maybe it is a kernel config then I will try to compile that version with Woof-CE kernel-kit, and test it under Puppy Linux. If it solve the problem, then it answer itself it is kernel config.

Anyway thanks for your answers!
Best wishes!

Ramachandra Iyer wrote: ↑Thu Jul 07, 2022 2:11 pm

.
.
As suggested by you, I have replaced wkg-uuid with wkg-de=nvme0nlp6. No such delay in finding drivers....... quick response. My error report image is given below:WhatsApp Image 2022-07-07 at 7.32.05 PM.jpeg

You have typed above nvme0nlp6 (with lower case 'L'), it should be nvme0n1p6 (with numeric 1).

No typo in cfg file. Please see error screen.

Ramachandra Iyer wrote: ↑Thu Jul 07, 2022 6:38 pm

No typo in cfg file. Please see error screen.

The photo shows that "fdisk: cannot open /dev/nvme0n1"

So the fundamental problem is still there, the drive is unusable.

nocsak wrote: ↑Thu Jul 07, 2022 2:13 pm

Aam - can I ask you to give me dotconfig of the EasyOS kernel somehow? If maybe it is a kernel config then I will try to compile that version with Woof-CE kernel-kit, and test it under Puppy Linux. If it solve the problem, then it answer itself it is kernel config.

In a running EasyOS, the kernel config is available in two places:

/etc/modules
/proc/config.gz