Nemesis update- v24.01 (2024-01-18)

[ncmprhnsbl]

..And it's another year.

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-01-18 (and mirrorlists set to corresponding package archive by default).

• New packages added, mpv/ffmpeg deps and possibly others..

• Kernel updated to 6.6.12 (Reminder: neko's kernel builder app works with nemesis if you want a newer or different or tuned to your hardware kernel : note 6.6. and 6.7 currently needs additional patching).

• Initrd.xz bug fixed regarding copy2ram (doubled entry for copying modules to ram).

• Pman and dir2xzm fixed for error of missing config.

• Cinnamon: included /etc/pacman.conf containing: "Ignorepkg = xreader" to avoid upgrading it for now. The new version is linked to webkit2gtk. Options are: drop it or custom build it without webkitgtk

[Ed_P]

What is the difference between the .iso files and the .delta files? The README.txt file doesn't clarify the difference between them.

[ncmprhnsbl]

What is the difference between the .iso files and the .delta files? The README.txt file doesn't clarify the difference between them.

.delta file is used to update the older iso .eg Nemesis-v23.09-to-v24.01-LXQT.delta can produce a Nemesis-v24.01-LXQT-x86_64.iso if applied to a Nemesis-v23.09-LXQT-x86_64.iso, if you happen to have one already.
this is done by either using the xdelta gui app in nemesis or directly with xdelta3 in a terminal (in the directory containing old file and delta) :

Code: Select all

# xdelta3 -s old_file_name old_to_new_delta_file new_file_name 
# xdelta3 -s Nemesis-v23.09-LXQT-x86_64.iso  Nemesis-v23.09-to-v24.01-LXQT.delta Nemesis-v23.09-LXQT-x86_64.iso

Added to the readme, thanks

[Jack]

When I try to boot in to Nemesis-v24.01-CINNAMON-x86_64.iso I receive this ERROR

--guest: /home/guest: change directory failed: Permission Denied

[beny]

hi jack, try ,you have to boot as root and change the permission on the home directory,but you can...if you have the changes activated rename the changes directory and make another one, the new nemesis have a lot of changes inside so a clean changes directory maybe is better for your system,but i can go wrong..

[ncmprhnsbl]

When I try to boot in to Nemesis-v24.01-CINNAMON-x86_64.iso I receive this ERROR

i'll need more information about this.
how are you trying to boot Nemesis-v24.01-CINNAMON-x86_64.iso?
is it installed? what does this installation look like?
and what beny says..

[Jack]

When I try to boot in to Nemesis-v24.01-CINNAMON-x86_64.iso I receive this ERROR

i'll need more information about this.
how are you trying to boot Nemesis-v24.01-CINNAMON-x86_64.iso?
is it installed? what does this installation look like?
and what beny says..

Here is my USB.

Code: Select all

/mnt/sdb2/EFI
/mnt/sdb2/[BOOT]
/mnt/sdb2/boot
/mnt/sdb2/USB_INSTALLATION.txt

/mnt/sdb1/config
/mnt/sdb1/porteus

That's how I boot and when I see the menu I pick Graphics mode(changes) after that I see
--guest: /home/guest: change directory failed: Permission Denied I haven't change any thing after I made the USB.

Hope this helps.

[M. Eerie]

Initrd.xz bug fixed

It seems the /boot/syslinux/porteus.cfg has changed and now the provided ISO's won't boot... Default Graphics mode results in an endless 9 seconds loop, while every other boot option does nothing at all.

There are two menu entries labelled "NEMESIS" in that file...

Forget it. Reverting to prior kernel (6.5-3) boots fine.


sha256sums for v.6.6.12:
0951f7d68fb01b9074457c130ae9d82565ee2597f22068bf5abd037045698683 000-kernel.xzm
33faac592bd3dd2bd0e66fb7d8073df4c5829c12776f9baf45f20fc3f0c37d9d 06-crippled_sources-6.6.12-64bit.xzm
43b15ff000bb71635751428d68780999c6f3d950ffa642a6ed1ba7e6b2db319b vmlinuz

[ncmprhnsbl]

Forget it. Reverting to prior kernel (6.5-3) boots fine.

what's your graphics hardware?

[ncmprhnsbl]

That's how I boot and when I see the menu I pick Graphics mode(changes) after that I see

pick the first one (without changes) and see what happens..
what's the output of :

Code: Select all

ls -l /mnt/sdb1/porteus/changes/home

?
by rights, there should probly be some mechanism to fix bad permissions of changes in the boot process, but it seems there isn't.

[Jack]

That's how I boot and when I see the menu I pick Graphics mode(changes) after that I see

pick the first one (without changes) and see what happens..
what's the output of :

Code: Select all

ls -l /mnt/sdb1/porteus/changes/home

?
by rights, there should probly be some mechanism to fix bad permissions of changes in the boot process, but it seems there isn't.

I can't bootup the latest version of Nemesis so I can't run .

Code: Select all

ls -l /mnt/sdb1/porteus/changes/home

[ncmprhnsbl]

I can't bootup the latest version of Nemesis so I can't run .

did you try: "pick the first one (without changes) and see what happens" that is: the first boot option on the boot screen.
or as beny suggested: boot with the login=root cheatcode (press tab at the boot screen and type login=root)
or boot porteus and mount your nemesis usb (which might be say sdc1) then run:

Code: Select all

ls -l /mnt/sdc1/porteus/changes/home

or whatever the correct sd*1 is.

[Jack]

I can't bootup the latest version of Nemesis so I can't run .

did you try: "pick the first one (without changes) and see what happens" that is: the first boot option on the boot screen.
or as beny suggested: boot with the login=root cheatcode (press tab at the boot screen and type login=root)
or boot porteus and mount your nemesis usb (which might be say sdc1) then run:

Code: Select all

ls -l /mnt/sdc1/porteus/changes/home

or whatever the correct sd*1 is.

I try to boot all menu. Just don't bootup.

Code: Select all

Graphics mode
Graphics mode (changes)
Always Fresh
copy2ram
Text mode
Text mode (safe)

[Ed_P]

Just don't bootup.

Please post a screen shot of what you see when you try to boot. If different messages for Graphics mode and Always Fresh please post an image of each.

[M. Eerie]

what's your graphics hardware?

Code: Select all

inxi -G
Graphics:
  Device-1: AMD Renoir [Radeon RX Vega 6 ] driver: amdgpu v: kernel
  Display: server: X.org v: 1.21.1.11 driver: X: loaded: amdgpu
    unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi gpu: amdgpu
    resolution: 1920x1080~60Hz
  API: OpenGL Message: Unable to show GL data. glxinfo is missing.

I have a notebook with Intel graphics as well. Gonna try there with kernel 6.6.12 and report.

Edit:
HP All in One with NVIDIA graphics BOOTS FINE with kernel 6.6.12:

Code: Select all

inxi -G
Graphics:
  Device-1: NVIDIA GF119M [GeForce 610M] driver: nouveau v: kernel
  Device-2: Realtek HP 1.0MP High Definition Webcam driver: uvcvideo
    type: USB
  Display: server: X.org v: 1.21.1.11 driver: X: loaded: nouveau
    unloaded: fbdev,modesetting,vesa dri: nouveau gpu: nouveau
    resolution: 1920x1080~70Hz
  API: OpenGL Message: Unable to show GL data. glxinfo is missing.
  

Laptop with INTEL graphics BOOTS FINE with kernel 6.6.12 too.