Porteus-v5.01 bug reports

[Ed_P]

The save-session function has problems. Something New (Post by Jack #98421)

[Rava]

1 Not a bug report per se.
I cannot find the link to the mirrors in the port main page. ( http://porteus.org/ )

I had to go back to the original post about Porteus-v5.0 is released! - only in there I found the mirror links- aka http://porteus.org/porteus-mirrors.html
And I knew it was somewhere in an older post. Newbies to Port might not be that understanding or willing to look for it.

In my book, that link should be restored to the main page and be put in every Announcements post when it is about files to be found on mirrors.
Or does the main page now need JavaScript enabled to show the mirrors link?

2 Anyhow, why are the most crucial updates - e.g. 001-* and 003-* only given a md5sum check file ( "updates.txt") , while the other files that are less crucial have the much more reliable sha256 checksums provided ( "sha256sums.txt" ) ?

[donald]

Hmmm..

The 5.01 64bit isos 06-Mar-2024 do not work as live-CD in my V-box
-- I get the boot-options-menu, then nothing.

but 5.01 32bit isos same date 06-Mar-2024 { kernel 6.6.20 ] are OK.

also 64bit 5.01 isos from 03-Oct-2023 do work.

[ncmprhnsbl]

I cannot find the link to the mirrors in the port main page

the dropdown menu links the the release announcement (although it needs to be updated to 5.01) which has the mirrors link .. the big 'download it' just links to the announcements area..
the updates are meant to accessed via the updater in the settings centre.

why are the most crucial updates - e.g. 001-* and 003-* only given a md5sum check file ( "updates.txt") , while the other files that are less crucial have the much more reliable sha256 checksums provided ( "sha256sums.txt" ) ?

because somebody hasn't got around to changing the updater script for that

The 5.01 64bit isos 06-Mar-2024 do not work as live-CD in my V-box
-- I get the boot-options-menu, then nothing.

hmm, they works here in my vbox.

[bour59]

I can't disconnect from the forum
I can't contact an administrator to help me to solve this isssue
thanks

[Rava]

the updates are meant to accessed via the updater in the settings centre.

I prefer to download it manually since I do want to keep the recent files as backup.

the dropdown menu links the the release announcement (although it needs to be updated to 5.01) which has the mirrors link .. the big 'download it' just links to the announcements area..

But there used to be a link on the man page to http://porteus.org/porteus-mirrors.html

[Ed_P]

I prefer to download it manually since I do want to keep the recent files as backup.

I believe the Settings Centre's Updater downloads any updates to the /tmp folder and then either reminds the user to copy them to the /porteus/base/ folder or asks the user if he/she wants it to copy them to the /porteus/base/ folder. Either way, the user has the opportunity to backup/rename files before the update is actually installed.

Try it.

[donald]

@ ncmprhnsbl
Yep, the new 64bit isos work in a slightly newer version of vbox.

But why is that?
It is clearly the new vmlinuz file in the new 64bit isos.
so what has changed between 5.01 03-Oct-2023 and 5.01 06-Mar-2024 64bit vmlinuz..
...compression mode??

The kernel version 6.6.20 is not the problem -- work in a 32bit iso.

[Rava]

downloads any updates to the /tmp folder and then either reminds the user to copy them to the /porteus/base/ folder or asks the user if he/she wants it to copy them to the /porteus/base/ folder. Either way, the user has the opportunity to backup/rename files before the update is actually installed.

My free space in /tmp is not large enough to hold both 001 and 002 file, currently that needed space is 235.08 MB

[Ed_P]

My free space in /tmp is not large enough to hold both 001 and 002 file, currently that needed space is 235.08 MB

Then direct the Settings Centre Updater to download to a folder with more space.

We can check for updates and download any to
a location of your choosing.

No need to manually do what the Updater does for you.

[Rava]

No need to manually do what the Updater does for you.

He does download 05-devel for me as well?

[Ed_P]

He does download 05-devel for me as well?

I don't know what files are covered by Updater. Easy enough for you to try and find out.

Added in 2 hours 27 minutes 42 seconds:
This file should answer your question:

Code: Select all

guest@porteus:/opt/porteus-scripts$ cat update-porteus
#!/bin/bash

# Copyright 2016-2020  Jay Flood, SP, Brasil
# All rights reserved.
  :
  :
  :

[ncmprhnsbl]

@ ncmprhnsbl
Yep, the new 64bit isos work in a slightly newer version of vbox.

But why is that?
It is clearly the new vmlinuz file in the new 64bit isos.
so what has changed between 5.01 03-Oct-2023 and 5.01 06-Mar-2024 64bit vmlinuz..
...compression mode??

The kernel version 6.6.20 is not the problem -- work in a 32bit iso.

when Blaze first compiled the 32bit version it failed to boot (somewhere around mounting the union if i remember correctly)
so i had a go at compiling it myself, tweaking the config... here's a diff:

Code: Select all

--- Blaze/32bit.config	2024-03-06 04:00:37.000000000 +1000
+++ mine/32bit.config	2024-04-30 17:58:03.000000000 +1000
@@ -213,8 +213,8 @@
 # CONFIG_BOOT_CONFIG_FORCE is not set
 # CONFIG_BOOT_CONFIG_EMBED is not set
 # CONFIG_INITRAMFS_PRESERVE_MTIME is not set
-CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y
-# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
+# CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE is not set
+CONFIG_CC_OPTIMIZE_FOR_SIZE=y
 CONFIG_LD_ORPHAN_WARN=y
 CONFIG_LD_ORPHAN_WARN_LEVEL="warn"
 CONFIG_SYSCTL=y
@@ -293,7 +293,7 @@
 CONFIG_X86_32_SMP=y
 CONFIG_ARCH_SUPPORTS_UPROBES=y
 CONFIG_FIX_EARLYCON_MEM=y
-CONFIG_PGTABLE_LEVELS=2
+CONFIG_PGTABLE_LEVELS=3
 CONFIG_CC_HAS_SANE_STACKPROTECTOR=y
 
 #
@@ -404,20 +404,21 @@
 CONFIG_X86_MSR=m
 CONFIG_X86_CPUID=m
 # CONFIG_NOHIGHMEM is not set
-CONFIG_HIGHMEM4G=y
-# CONFIG_HIGHMEM64G is not set
+# CONFIG_HIGHMEM4G is not set
+CONFIG_HIGHMEM64G=y
 CONFIG_VMSPLIT_3G=y
-# CONFIG_VMSPLIT_3G_OPT is not set
 # CONFIG_VMSPLIT_2G is not set
-# CONFIG_VMSPLIT_2G_OPT is not set
 # CONFIG_VMSPLIT_1G is not set
 CONFIG_PAGE_OFFSET=0xC0000000
 CONFIG_HIGHMEM=y
+CONFIG_X86_PAE=y
 # CONFIG_X86_CPA_STATISTICS is not set
 CONFIG_ARCH_FLATMEM_ENABLE=y
 CONFIG_ARCH_SPARSEMEM_ENABLE=y
 CONFIG_ARCH_SELECT_MEMORY_MODEL=y
 CONFIG_ILLEGAL_POINTER_VALUE=0
+CONFIG_X86_PMEM_LEGACY_DEVICE=y
+CONFIG_X86_PMEM_LEGACY=y
 # CONFIG_HIGHPTE is not set
 # CONFIG_X86_CHECK_BIOS_CORRUPTION is not set
 CONFIG_MTRR=y
@@ -469,6 +470,7 @@
 CONFIG_FUNCTION_PADDING_CFI=0
 CONFIG_FUNCTION_PADDING_BYTES=4
 CONFIG_SPECULATION_MITIGATIONS=y
+CONFIG_PAGE_TABLE_ISOLATION=y
 CONFIG_RETPOLINE=y
 CONFIG_RETHUNK=y
 # CONFIG_GDS_FORCE_MITIGATION is not set
@@ -618,7 +620,6 @@
 CONFIG_ISA_DMA_API=y
 # CONFIG_ISA is not set
 # CONFIG_SCx200 is not set
-# CONFIG_OLPC is not set
 # CONFIG_ALIX is not set
 # CONFIG_NET5501 is not set
 # CONFIG_GEOS is not set
@@ -741,6 +742,7 @@
 CONFIG_HAVE_MOVE_PUD=y
 CONFIG_HAVE_MOVE_PMD=y
 CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=y
+CONFIG_HAVE_ARCH_HUGE_VMAP=y
 CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y
 CONFIG_ARCH_WANT_PMD_MKWRITE=y
 CONFIG_HAVE_MOD_ARCH_SPECIFIC=y
@@ -776,6 +778,7 @@
 CONFIG_ARCH_SPLIT_ARG64=y
 CONFIG_ARCH_HAS_PARANOID_L1D_FLUSH=y
 CONFIG_DYNAMIC_SIGFRAME=y
+CONFIG_ARCH_HAS_NONLEAF_PMD_YOUNG=y
 
 #
 # GCOV-based kernel profiling
@@ -949,12 +952,14 @@
 CONFIG_EXCLUSIVE_SYSTEM_RAM=y
 CONFIG_ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE=y
 CONFIG_SPLIT_PTLOCK_CPUS=4
+CONFIG_ARCH_ENABLE_SPLIT_PMD_PTLOCK=y
 CONFIG_MEMORY_BALLOON=y
 CONFIG_BALLOON_COMPACTION=y
 CONFIG_COMPACTION=y
 CONFIG_COMPACT_UNEVICTABLE_DEFAULT=1
 CONFIG_PAGE_REPORTING=y
 CONFIG_MIGRATION=y
+CONFIG_PHYS_ADDR_T_64BIT=y
 CONFIG_BOUNCE=y
 CONFIG_MMU_NOTIFIER=y
 # CONFIG_KSM is not set
@@ -980,6 +985,7 @@
 # CONFIG_VM_EVENT_COUNTERS is not set
 # CONFIG_PERCPU_STATS is not set
 # CONFIG_GUP_TEST is not set
+CONFIG_GUP_GET_PXX_LOW_HIGH=y
 # CONFIG_DMAPOOL_TEST is not set
 CONFIG_ARCH_HAS_PTE_SPECIAL=y
 CONFIG_MAPPING_DIRTY_HELPERS=y
@@ -6393,7 +6399,6 @@
 #
 # USB Peripheral Controller
 #
-# CONFIG_USB_FUSB300 is not set
 # CONFIG_USB_GR_UDC is not set
 # CONFIG_USB_R8A66597 is not set
 # CONFIG_USB_PXA27X is not set
@@ -6803,6 +6808,7 @@
 CONFIG_VIRTIO_MENU=y
 CONFIG_VIRTIO_PCI=m
 CONFIG_VIRTIO_PCI_LEGACY=y
+CONFIG_VIRTIO_PMEM=m
 CONFIG_VIRTIO_BALLOON=m
 CONFIG_VIRTIO_INPUT=m
 CONFIG_VIRTIO_MMIO=m
@@ -7165,6 +7171,13 @@
 # CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set
 # end of Android
 
+CONFIG_LIBNVDIMM=y
+CONFIG_BLK_DEV_PMEM=y
+CONFIG_ND_CLAIM=y
+CONFIG_ND_BTT=y
+CONFIG_BTT=y
+CONFIG_NVDIMM_KEYS=y
+# CONFIG_NVDIMM_SECURITY_TEST is not set
 CONFIG_DAX=y
 # CONFIG_DEV_DAX is not set
 CONFIG_NVMEM=y
@@ -7385,9 +7398,9 @@
 # CONFIG_VBOXSF_FS is not set
 CONFIG_AUFS_FS=y
 # CONFIG_AUFS_BRANCH_MAX_127 is not set
-# CONFIG_AUFS_BRANCH_MAX_511 is not set
+CONFIG_AUFS_BRANCH_MAX_511=y
 # CONFIG_AUFS_BRANCH_MAX_1023 is not set
-CONFIG_AUFS_BRANCH_MAX_32767=y
+# CONFIG_AUFS_BRANCH_MAX_32767 is not set
 CONFIG_AUFS_SBILIST=y
 CONFIG_AUFS_HNOTIFY=y
 CONFIG_AUFS_HFSNOTIFY=y
@@ -7781,7 +7794,6 @@
 CONFIG_CRYPTO_DEV_PADLOCK_AES=m
 CONFIG_CRYPTO_DEV_PADLOCK_SHA=m
 # CONFIG_CRYPTO_DEV_GEODE is not set
-# CONFIG_CRYPTO_DEV_HIFN_795X is not set
 # CONFIG_CRYPTO_DEV_ATMEL_ECC is not set
 # CONFIG_CRYPTO_DEV_ATMEL_SHA204A is not set
 CONFIG_CRYPTO_DEV_CCP=y
@@ -7924,6 +7936,7 @@
 CONFIG_NEED_SG_DMA_FLAGS=y
 CONFIG_NEED_SG_DMA_LENGTH=y
 CONFIG_NEED_DMA_MAP_STATE=y
+CONFIG_ARCH_DMA_ADDR_T_64BIT=y
 CONFIG_SWIOTLB=y
 # CONFIG_SWIOTLB_DYNAMIC is not set
 # CONFIG_DMA_API_DEBUG is not set
@@ -7951,6 +7964,7 @@
 CONFIG_FONT_8x8=y
 CONFIG_FONT_8x16=y
 CONFIG_SG_POOL=y
+CONFIG_MEMREGION=y
 CONFIG_ARCH_HAS_CPU_CACHE_INVALIDATE_MEMREGION=y
 CONFIG_ARCH_STACKWALK=y
 CONFIG_SBITMAP=y
@@ -8043,9 +8057,7 @@
 # CONFIG_SHRINKER_DEBUG is not set
 # CONFIG_DEBUG_STACK_USAGE is not set
 # CONFIG_SCHED_STACK_END_CHECK is not set
-CONFIG_ARCH_HAS_DEBUG_VM_PGTABLE=y
 # CONFIG_DEBUG_VM is not set
-# CONFIG_DEBUG_VM_PGTABLE is not set
 CONFIG_ARCH_HAS_DEBUG_VIRTUAL=y
 # CONFIG_DEBUG_VIRTUAL is not set
 # CONFIG_DEBUG_MEMORY_INIT is not set

not all it relevant to the boot issue eg. the PAE stuff i added after the booting was fixed, to see all of my memory..
this:

Code: Select all

-CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y
-# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
+# CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE is not set
+CONFIG_CC_OPTIMIZE_FOR_SIZE=y

seems to make the modules much smaller(and most likely a smaller memory footprint)
reducing the max aufs branches may had an effect on the problem..
not sure, i was les than systematic in my approach

[donald]

Thank you for looking at it.

So the 32bit-iso boots after you modified the config - and is compatible/working in 'my' v-box.
...the unmodified 64bit iso is not compatible.

I wish I had a more powerful PC - to compile the 64bit kernel with the configuration
from the earlier 5.01 version, which is compatible.

For now, I have to leave it as it is.

[Ed_P]

I like the updates to the new 001-core and 002-xorg 64bit modules ncmp. Did the pmod & slapt-mod changes get made to other scripts also?