Nemesis update- v24.06 (2024-06-17)

[ncmprhnsbl]

Overdue again
ISOs available here: ISO Downloads
Modules here: Module Downloads
05-devel here: 05-devel Download
Kernel and crippled sources: Kernel Downloads

Changelog:

• Packages updated to 2024-06-17 (and mirrorlists set to corresponding package archive by default).

• Kernel updated to 6.9.5

• Activate scripts updated to correspond to porteus version, backported to gtkdialog

• Porteus-installer-for-linux legacy bios bootloader installer updated ~ should now be more tolerant of diverse mounting locations

• Edited boot/docs/install.txt to be more accurate/relevant and added a section for UEFI

• LXQT: now version 2.0 using qt6. (which is a bit fatter than qt5 : beware: I've stripped a bunch of stuff, so it's possible there could be breakage of other packages you might want that require qt6-base. I'll see if i can get together a couple of modules with dev and the extra stuff.

• Cinnamon: removed fileroller(avoid gtk4), removed gnome-terminal(theme issues), removed hypnotix, added engrampa and mate-terminal , added CBlack and Orchis-Light themes (wasn't playing nice with adwaita), updated zenity-light and xreader without webkit

Known issues:

• syslog-ng makes some noise about missing libs to do with optional plugins ..some way of configuring this out rather then adding all that stuff would be good

• Lxqt panel clock is somewhat broken

• The language modules havn't been updated yet, so lxqt and cinnamon will have spotty support until i do so.

• bad path syntax in /boot/syslinux/porteus.cfg for UEFI booting>fixed

[Ed_P]

Wow! You've been busy. Thank you.

[Porcino]

I was waiting for this update
I have one problem, I can't boot from UEFI, it get stuck in the menu and the countdown restarts, if I want to reboot it says reboot.c32 not found. @roadie said the path of vmlinux and initrd.xz was worng so I added to the default /boot/syslinux/ to both and it just load those files and then it get stuck.
I clarify that porteus boot just fine but nemesis doesn't, and this happens on 3 different pcs.

[ncmprhnsbl]

I have one problem, I can't boot from UEFI, it get stuck in the menu and the countdown restarts, if I want to reboot it says reboot.c32 not found. @roadie said the path of vmlinux and initrd.xz was worng so I added to the default /boot/syslinux/ to both and it just load those files and then it get stuck.

yes, the porteus.cfg needs fixing to :

Code: Select all

KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND

which works for my test.. not sure what's going on for you.. i'll fix the isos and reupload.(done)
and yes reboot won't work for uefi and possibly other scenarios (as the help message says) (ctl+alt+delete or ctl+alt+prscn+r/o will sometimes work)
thanks for the report

[Ed_P]

It would be nice if Netsurf had a link to the Porteus Forum's Active_Topics.

It would also be nice for Netsurf to support access to the forum's Quick Links options.

I can't boot from UEFI

Your system on a FAT32 drive?

[Porcino]

Your system on a FAT32 drive?

Yes.
I just tried the new iso, it load both vmlinux and initrd.xz and then it freezes

[M. Eerie]

it load both vmlinux and initrd.xz and then it freezes

The same thing happens to me. It seems that the new kernel 6.9.5 does not boot. Try changing both /boot/syslinux/vmlinuz and /porteus/base/000-kernel.xzm to the previous version. It worked for me

[ncmprhnsbl]

It seems that the new kernel 6.9.5 does not boot.

some hardware anomaly in common, i guess. (that neither me or Ed has)
i did compile 6.9.5 with old firmware, so this could be the problem.
so i recompiled 6.9.5 with the latest firmware and uploaded it to https://sourceforge.net/projects/nemesi ... nel/6.9.5/
also, if that still doesn't work, i also uploaded the LTS 6.6.34 to : https://sourceforge.net/projects/nemesi ... el/6.6.34/
i included the config too if you can see anything in there that might be the problem.
if either if those kernels works for you, i'll update the ISOs with one of them.

It would be nice if Netsurf had a link to the Porteus Forum's Active_Topics.
It would also be nice for Netsurf to support access to the forum's Quick Links options.

menu>system>Nemesis-FAQ links to this forum (at the top)
netsurf has limited functionality for general webbrowsing and is only meant as a stopgap that may help in troubleshooting,
slightly more user friendly than lynx, until the user adds their preferred browser.
hint:

Code: Select all

#setup-pman
#pmod firefox

[M. Eerie]

if either if those kernels works for you, i'll update the ISOs with one of them.

Unfortunately, neither of them worked for me. Interestingly, I have converted the 6.9.4 kernel from Porteux and it does work for me. Although it lacks /usr/bin/cryptsetup

This is the configuration that uses.

The other one I was working with is version 6.8.9 with this config

Thanks

[beny]

hi M.Eeire Mr Neko, he have release the new kernel builder take a try to build something that is useful

[M. Eerie]

new kernel builder take a try

Thanks beny. I'll try it later. Which config would I need to build the LTS (6.6.34) or the stable one (6.9.5) ?

[beny]

hi, config are included into the software you have to choose the environment:you have slackware and arch,nemesis is an arch based system so...and you have the last version of all kernel branch,the devel package is mandatory for this task
ps:the kernel builder work with the 6.9.5 kernel version on the porteux v-1.4.

[roadie]

I'm playing with Nemesis, using the latest version. I've installed it as a frugal install, same way I do with Porteus and PorteuX. Arch systems are basically new to me as I haven't used Nemesis in years.

I tried to run setup-config-pman and I get the "not writable" error while setup-pman works well, I'm assuming because it doesn't write to the config folder. It's not a big deal as setup-pman lets me get stuff I want, more just curiosity as to why it doesn't see the partition as writable.......I've confirmed it is writable. It's looking at the right partition, though I saw a post that made me wonder if the config folder should be in the partition holding the kernel, I hope that's not the case as I don't want things being written to it.

[M. Eerie]

new kernel builder take a try to build

I've successfully built the 6.9.6 kernel, but unfortunately the result is the same as with the ones provided by ncmprhnsbl. The system hangs and I have to power-off.

Things to note:
* The vmlinuz filesize is 8.1 Mb, while the working one (6.8.10 from Blaze) is 9.9 Mb
* The crippled-sources filesize is weirdly bigger than usual 41.7Mb vs 23.6Mb

If anyone is interested, this is the link to the tar file including vmlinuz, crippled sources, kernel module and 64bit.config

sha256sum: c48996d084dad876b003cc8c799c74b004334b291d4e0c3fecd97284a4c6d5c8

Thanks.

[ncmprhnsbl]

The system hangs and I have to power-off.

that if fails so early in the boot, suggests to me that it's something in the config (as opposed to missing firmware, which wouldn't come into play until after the modules are loaded)
diff eyeballing the configs you provided compared with mine(which is nekos, since i'm just using the kernel builder), nothing jumped out as obvious, but i'm no expert.
initial looking at fulalas kernel build script, i don't see anything standout either (there's some sof firmware added but i don't think that's the problem here and the make flags/stripping shouldn't be relevant)
next step for me will be to build(with the kernel builder) using one the configs you provided.
then, if that doesn't work, try to adapt fulalas script for arch filesystem and try that.
RE: the size difference is most probably down to using (sic)optimize_for_performance rather than optimize_for_size

made me wonder if the config folder should be in the partition holding the kernel, I hope that's not the case as I don't want things being written to it.

in my setup, i have vmlinuz,initrd.xz on a fat32 boot partition and config,porteus on an ext partition, so yes /config must reside with /porteus.
i can't say i've used/looked at setup-config-pman, will check, might be some faulty read/write test.
it's quite easy to manually edit any of the files in config/ , they're well commented and fairly self explanatory.