Page 18 of 20
2021 Updated Nemesis Base Modules
Posted: 17 Nov 2021, 21:02
by M. Eerie
There's no package containing that file in Archlinux:
https://archlinux.org/packages/?sort=&q=libcvt
Are you sure you are not mixing packages from Arch / Slackware?
2021 Updated Nemesis Base Modules
Posted: 17 Nov 2021, 21:30
by beny
M.Eerie exist:
NAME
cvt - calculate VESA CVT mode lines
SYNOPSIS
cvt [-v|--verbose] [-r|--reduced] h-resolution v-resolution [refresh]
DESCRIPTION
Cvt is a utility for calculating VESA Coordinated Video Timing modes. Given the desired horizontal and vertical resolutions, a modeline adhering to the CVT standard is printed. This modeline can be included in Xorg xorg.conf(5)
2021 Updated Nemesis Base Modules
Posted: 17 Nov 2021, 22:06
by Jack
I use your 001-core, 002-gui and 002-xtra and I built 003-mate. I only use Arch and
no to Slackware. Beside I wanted everything to work.
2021 Updated Nemesis Base Modules
Posted: 17 Nov 2021, 23:07
by ncmprhnsbl
looks like a recent addition: new xorg-server dep: libxcvt
most likely only used for some graphics cards..
2021 Updated Nemesis Base Modules
Posted: 18 Nov 2021, 07:00
by M. Eerie
Thanks @beny and @ncmprhnsbl
@Jack
You only need to add the needed package to this section of the
update-base script.
M. Eerie wrote: ↑10 Nov 2021, 12:52
case $bMOD in
*lxde|*lxqt|*xfce|*mate) pkgAdd=""; pkgRem="";;
*xtra) pkgAdd=""; pkgRem="";;
*
gui) pkgAdd="
libxcvt"; pkgRem="";;
*devel) pkgAdd=""; pkgRem="";;
*core) pkgAdd=""; pkgRem="";; ### --ignore '*'
end*) the_end;;
esac
Once 002-gui module is updated with the new libxcvt package, just revert back to not trying to reinstall it again and again.
From time to time, a new dependency is needed and this is how new additions are handled
2021 Updated Nemesis Base Modules
Posted: 18 Nov 2021, 08:48
by Jack
M. Eerie wrote: ↑18 Nov 2021, 07:00
Thanks @beny and @ncmprhnsbl
@Jack
You only need to add the needed package to this section of the
update-base script.
M. Eerie wrote: ↑10 Nov 2021, 12:52
case $bMOD in
*lxde|*lxqt|*xfce|*mate) pkgAdd=""; pkgRem="";;
*xtra) pkgAdd=""; pkgRem="";;
*
gui) pkgAdd="
libxcvt"; pkgRem="";;
*devel) pkgAdd=""; pkgRem="";;
*core) pkgAdd=""; pkgRem="";; ### --ignore '*'
end*) the_end;;
esac
Once 002-gui module is updated with the new libxcvt package, just revert back to not trying to reinstall it again and again.
From time to time, a new dependency is needed and this is how new additions are handled
I just copy the script again because I seen you must have edit it. I added that line
*gui) pkgAdd="libxcvt"; pkgRem="";; and the one was all ready there I put
# in front of it. After I updated 002-gui I will change the
# to the line I just added. Thanks
2021 Updated Nemesis Base Modules
Posted: 18 Nov 2021, 19:36
by Jack
Well I rebuild them all with your fix added. Then I rebooted to a black screen so I ran update-cache I move the module to /porteus/base. After I move it I rebooted to another black screen. I'm just letting you know.
2021 Updated Nemesis Base Modules
Posted: 19 Nov 2021, 09:14
by M. Eerie
There's really no need to rebuild ALL the modules, but the one you are trying to update (002-gui).
That said, check out for other missing dependencies. My advice:
Get back in time and start fresh (no other modules) from the last build, then try to update and review the messages from the pacman.log to track new dependencies.
2021 Updated Nemesis Base Modules
Posted: 19 Nov 2021, 20:06
by Jack
M. Eerie wrote: ↑19 Nov 2021, 09:14
Get back in time and start fresh (no other modules) from the last build, then try to update and review the messages from the pacman.log to track new dependencies.
Well I started over what you said here. I did update in this order 003-mate, 002-xtra, 002-gui, 05-devel and 001-core. but I do have a 003-xtra which has mate extra in it. If you want to look at my
pacman.log I can post it.
It now works like before but up to date now.
You are the man and thank you for it.
2021 Updated Nemesis Base Modules
Posted: 20 Nov 2021, 00:44
by Jack
Well I did some testing as long as you don't add any porgrams modules everything work but if you add Firefox or any other when it boot up you get a black screen and only way to get out is hit the main power button. That's what I seen so far. I will test by putting in old 001-core.
EDIT: Well I change to 001-core-20211006.xzm but I boot up error libffi.so.8 so I can't test it.
2021 Updated Nemesis Base Modules
Posted: 20 Nov 2021, 08:40
by M. Eerie
Jack wrote: ↑20 Nov 2021, 00:44
I boot up error libffi.so.8 so
I've faced this one too. Just (re-)install libffi into your 001-core module:
Code: Select all
case $bMOD in
*lxde|*lxqt|*xfce|*mate) pkgAdd=""; pkgRem="";;
*xtra) pkgAdd=""; pkgRem="";;
*gui) pkgAdd=""; pkgRem="";;
*devel) pkgAdd=""; pkgRem="";;
*core) pkgAdd="libffi"; pkgRem="";; ### --ignore '*'
end*) the_end;;
esac
Jack wrote: ↑19 Nov 2021, 20:06
I did update in this order 003-mate, 002-xtra, 002-gui, 05-devel and 001-core
Note that updating 05-devel is not fully tested. The strip routine still needs to be adjusted.
Jack wrote: ↑19 Nov 2021, 20:06
but I do have a 003-xtra which has mate extra
I would suggest you to rename that module to 003-mate-extras or something to avoid confusion...
Also, you can customize the script to remaster YOUR MATE by doing these corrections:
M. Eerie wrote: ↑10 Nov 2021, 12:52
##
##
##
####### ####### ### UPDATE PACKAGES
##
##
##
updateBASE() {
clear
[ -d /tmp/updBASE ] || prepareSYS
cd /tmp/updBASE || exit
[ -d LOCALES ] || mkdir -p LOCALES
PS3=$'\n'$'\e[00;36mPlease, select base module to update or exit (1-
97): \e[0m'
select bMOD in
003-lxde 003-lxqt 003-mate-extras 003-mate
003-xfce 002-xtra 002-gui 05-devel 001-core end
do
pkgAdd=""
pkgRem=""
case $bMOD in
*mate-extras) pkgAdd=""; pkgRem="";;
*lxde|*lxqt|*xfce|*mate) pkgAdd=""; pkgRem="";;
*xtra) pkgAdd=""; pkgRem="";;
*gui) pkgAdd=""; pkgRem="";;
*devel) pkgAdd=""; pkgRem="";;
*core) pkgAdd=""; pkgRem="";; ### --ignore '*'
end*) the_end;;
esac
break
done
2021 Updated Nemesis Base Modules
Posted: 20 Nov 2021, 17:53
by beny
hi M.Eeire just for a try i have upgraded an old nemesis and your script work very well, i have upgraded all the packages and now is running without issue thanks.next step i change the kernel version...
2021 Updated Nemesis Base Modules
Posted: 20 Nov 2021, 20:02
by M. Eerie
Thanks for the feedback,
beny.
beny wrote: ↑20 Nov 2021, 17:53
next step i change the kernel version...
For kernel, you can use directly any APorteus kernel.
I'm using Linux porteus 5.15.2-porteus by now. And I see now
5.15.3 it's available.
Thanks to neko & blaze for their support on this.
2021 Updated Nemesis Base Modules
Posted: 20 Nov 2021, 23:21
by Rava
It seems Nemesis has issues with using runlevel 3. Is Nemesis really unable to handle runlevel 3?
I did not set up my digicam correctly so it cut off a bit from the very left side of the screen during boot.
I edited the screenshot to move the rightmost [ !! ] or [okay] messages more to the left to make it easier to see the info in the forum (I just removed the empty dark space between the info text left and the [ !! ] or [okay] messages right).
See for yourself:
I tried finding the Network manager error in dmesg or /var/log/messages.log but to no prevail:
as guest
Code: Select all
guest@porteus:~$ dmesg |grep -i net
[ 0.252422] NET: Registered protocol family 16
[ 0.393184] NET: Registered protocol family 2
[ 0.394967] NET: Registered protocol family 1
[ 0.674836] usbcore: registered new interface driver ums-onetouch
[ 0.723267] NET: Registered protocol family 17
[ 25.563421] NET: Registered protocol family 31
[ 384.432627] NET: Registered protocol family 10
as root
Code: Select all
root@porteus:~# grep -i net /var/log/messages.log
Nov 20 21:01:29 localhost kernel: NET: Registered protocol family 10
Used kernel:
5.12.18-porteus
using these modules:
000-kernel5.12.18-porteus.xzm
001-core-20211006.xzm
002-gui-20211006.xzm
002-xtra-20211006.xzm
003-xfce4-20211005.xzm
(I renamed the 000- module)
Added in 3 minutes 21 seconds:
Also, regardless if I do a restart via root Virtual terminal by typing restart or use Ctrl+Alt+Shift+Del to restart, each time the ext3 filesystems need to be checked since nemesis seems unable to umount the drives prior restarting.
2021 Updated Nemesis Base Modules
Posted: 21 Nov 2021, 03:54
by Jack
I did another test here is what did.
I went to the store and bought another 2 USB3.1 32gb so I can install Nemesis Mate on.
Well I install Nemesis Mate on it but it didn't have save changes directoy on it. Here is what I did.
1 First bootup I ran in Graphics mode then I receive a black screen so I hit Ctrl Alt F4 then I type in user and password then startx everything went great after that.
2 Second bootup I ran in Graphics mode then I receive another black screen so I try Ctrl Alt F4 that didn't work.
3 Third bootup I ran in Always Fresh that time everything went great.
4 Forth bootup same as number 2.
My question when it created the changes directory could that have something to do with it?