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

[ncmprhnsbl]

AMD Renoir [Radeon RX Vega 6 ]

hmm, i have an AMD Rembrandt [Radeon 680m] (also using amdgpu) that works ok with the 6.6.12 kernel.. and my nvidia desktop box..

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

any boot option you try should include the from= cheatcode, right? so for sdb1, that would be from=/dev/sdb1
even better is to use the UUID, which you should be able to get using blkid .. so: from=UUID:sTrIngOfnUmbers

[M. Eerie]

Can you share the config used to build the kernel?

[ncmprhnsbl]

Can you share the config used to build the kernel?

here you go: 64bit.config
it's just the "PROTO" config used by neko's kernel builder..

[Jack]

I have Nemesis Cinnamon up and running. I took my Mate and my Cinnamon USB. I took both USB and look at permissons I look at one that work then the one didn't work and change permisson. Now it boots and seem work.

[Ed_P]

[Otto]

Nemesis-v24.01-XFCE-x86_64.iso
No Wifi for Network device [0280] Broadcom Inc. and subsidiaries BCM4313 802.11bgn Wireless Network Adapter [14e4:4727] (rev 01)
• Kernel Driver bcma-pci-bridge
How to fix it?
Thanks

[ncmprhnsbl]

Nemesis-v24.01-XFCE-x86_64.iso
No Wifi for Network device [0280] Broadcom Inc. and subsidiaries BCM4313 802.11bgn Wireless Network Adapter [14e4:4727] (rev 01)
• Kernel Driver bcma-pci-bridge
How to fix it?
Thanks

(moved your post for better visibility)
according to this post: Nemesis 2023 (Post by Porcino #94697)

Solution was easy, with the crippled sources module, install with pacman 'broadcom-wl-dkms' and save changes to a module

might also work for you.. make sure you running without saved changes to do it and probly need to activate the 05-devel module too ( '# get-devel' command should fetch it for you)

[gaspro]

Im sorry I cant install.
Let me explain my problem:
boot from CD under virtualbox, then use installer, flag both, turn off machine, get out cd.
Using vanilla porteus no problems.
Using nemesis it says no operating system. For sake of completeness, I start graphical with changes, if that matters.

I really need the arch based because its easier to build packages and find the programs I need.

[ncmprhnsbl]

Im sorry I cant install.
Let me explain my problem:
boot from CD under virtualbox, then use installer, flag both, turn off machine, get out cd.
Using vanilla porteus no problems.
Using nemesis it says no operating system. For sake of completeness, I start graphical with changes, if that matters.

so assuming you are installing to a virtual disk in virtualbox, i think i can reproduce this.
i my case after installing, shutting down and ejecting cd/iso, i can reboot the virtual HD install first time ok, but then shutting down, booting the second time, it fails as you describe.
my guess is that the (lack of proper) shutdown procedure is corrupting the virtual HD or it's MBR at least. (probably due to improper dismounting of the drive, and maybe that vdi s are particularly sensitive to this)
i think this because, if (after reformatting and reinstalling) i booted using copy2ram cheatcode and it seemed to be ok, rebooting(multiple) no problem.
if this works for you, the good news is that copy2ram cheatcode works with changes= (be sure to hit tab at the boot menu to edit it the first time you boot after installation, then edit /boot/syslinux/porteus.cfg after you've booted.
but if you couldn't even boot the first time after installation, that i couldn't reproduce.

[Blaze]

I builded kernel 6.8.4 for Nemesis
Link for download https://www.mediafire.com/file/w63gcsvr ... l6.8.4.tar

[Porcino]

Hi, I'm having trouble booting nemesis from uefi, it get stuck in the menu, the countdown restart. Any other porteus version works, do you know why? and if there's a workaround

[roadie]

Hi, I'm having trouble booting nemesis from uefi, it get stuck in the menu, the countdown restart. Any other porteus version works, do you know why? and if there's a workaround

That usually indicates that either the kernel or initrd.xz is not being found. Press the TAB key and check that things are correct on the command line.

[dreadbird]

Im sorry I cant install.
Let me explain my problem:
boot from CD under virtualbox, then use installer, flag both, turn off machine, get out cd.
Using vanilla porteus no problems.
Using nemesis it says no operating system. For sake of completeness, I start graphical with changes, if that matters.

I really need the arch based because its easier to build packages and find the programs I need.

Can confirm it corrupts the mbr on the vdi. The solution I found is to boot in format your vdi and install porteus on it with the installer. Then grab firefox and what modules your want put them in the modules folder. Edit your /boot/syslinux/porteus.cfg. changes=/mnt/sda1/changes extramod=/mnt/sda1/extramod timezone=America/Vancouver

The timezones can be found in /usr/share/zoneinfo

Set it up how you want it then we create an .iso of it. /mnt/sda1/porteus/make_iso.sh. Take that and upload it to a clouddrive so you can download it on your host. Then you can boot off of that. Your vdi will not be effected on shutdown afterwards

dont forget to create the changes and extramod folder on /mnt/sda1/ after making the iso

[dreadbird]

I found another way to run on virtual box thats really easy.

Boot into nemesis and go to gparted. Create partition table GPT and then make a fat32 500MB. go to flags and select boot and esp. Then create a second partition as ext4 with the rest of the drive. Go to nemesis installer and install it to the second drive. Then copy all the folders except config and porteus to the first partition.

create a folder called changes on sda2

then on the first partiton go to /boot/syslinux/porteus.cfg

Add the changes folder and the porteus location
APPEND changes=/mnt/sda2/changes From=/mnt/sda2/porteus

Lastly in virtual box select enable EFI on the first setting page.

Then you can boot nemesis and the bootloader wont get touched like MBR (Only applies to .vdi and virtual box)

See my post about increasing the video memory to 256mb at the bottom
[HOWTO] Setup VirtualBox Guest Addition Module, Shared Folders and Clip-board (Post by dreadbird #101607)


As a side note 

My take on MBR and GPT. One or the other is easy a few clicks in gparted and done. What is not so straight foward is grub2. I played around with it by having debian install grub2 to a .vdi. Then I edited the config to boot porteus MBR. Im sure if I played around with it enough I could do GPT as well. But you have to ask yourself should you even bother learning all that? Syntax and commands that are not straight foward. An implementation that doesnt recognize porteus as an os?

Im my opinion any program that breaks at the slightest configuration misalignment is laughable. you make a program you make a guide to use it. A guide should not contain useless commands and if a command is listed explain what it does. This is why the arch wiki to me is useless. Therefor let the distributions like ubuntu and debian configure it for you. Im thankful porteus doesnt use grub2 because it may be great in the eyes of a software engineer or programmer but is not useful for the user.


Lets show the stanza or boot entry for grub bootloader if you were to use one

You would have two seperate harddrives not mixing MBR or gpt

Add these to custom 40 .cfg ( or convert them to actual menu entry with grub customizer)

#this boots porteus MBR Tested this works
menuentry "Porteus5.01" {
set root='(hd0,1)'
search --no-floppy --fs-uuid --set=root 66DD-8703
linux /boot/syslinux/vmlinuz changes=UUID:c012e6fd-3881-4876-bef8-12685e4b1b75/changes12
initrd /boot/syslinux/initrd.xz
}

Different drive

#GPT Tested also works
menuentry "Porteus Nemesis"{
set root='(hd0,1)'
search --no-floppy --fs-uuid --set=root putuuid here

chainloader /EFI/boot/bootx64.efi
#chainloader (${root})/EFI/boot/bootx64.efi #Use this if above doesntwork
}

[Ed_P]

Two grub2 menus for my Porteus 5.01 FAT32 USB drive.

Code: Select all

menuentry " Porteus 5.0 USB - EFI" --class slackware   --class user-icon-porteus  {

     set bootmgr=/EFI/boot/bootx64.efi         

     set bootdrv=$root
     search -f $bootmgr --set=root
     echo USB: $root
     sleep -v -i 4
     if [ $root != $bootdrv ]; then
        chainloader $bootmgr
     else
        echo "----------------------------------------"
        echo USB drive NOT found.
        echo
        sleep -v -i 10
     fi
     set root=$bootdrv
     }

menuentry " Porteus 5.0 USB - AF'" --class slackware   --class user-icon-porteus  {

     set bootparms="volume=33 reboot=cold extramod=/Modules" 

     set bootdrv=$root
     search -f /boot/syslinux/vmlinuz --set=root
     if [ $root != $bootdrv ]; then
        linux  /boot/syslinux/vmlinuz $bootparms
        initrd /boot/syslinux/initrd.xz
     else
        echo "----------------------------------------"
        echo USB drive NOT found.
        echo
        sleep -v -i 10
     fi
     set root=$bootdrv
     }

Not that hard to set up. The top menu brings up the porteus.cfg menu, the bottom menu boots directly to the Porteus DE.

The hardest part can be determining the value for root. IMO It is better to search for the drive being booted than assign a suspected drive letter, which may be wrong. Another option is using the drive's UUID code. A grub2 menu with something like this can help:

Code: Select all

     set USB_drv=/boot/syslinux/vmlinuz     # Can be a unique user named file on the drve.  "My1stPorteusUSB.txt"

     echo "Boot drive: "$root
     echo " "
     search -f $USB_drv --set=root
     if [ $? = 0 ]; then
        echo "USB drive:  "$root
        probe -u $root --set=USBuuid
        echo "UUID: "$USBuuid
        echo " "
        echo " "
        sleep -i -v 30 ; echo
     else
        echo "----------------------------------------"
        echo " "
        echo "No USB drive found."
        echo " "
        ls ; echo
        sleep -i -v 10 ; echo
     fi