Porteus-v4.0 bug reports

[ncmprhnsbl]

would an upgradepkg with ca-certificates-20211216-noarch-1_slack14.2 on an extracted 001-core do the update-ca-certificates -f ?

even though that's in the doinst.sh i don't think that sort of thing works in the fakeroot context..

[Rava]

even though that's in the doinst.sh i don't think that sort of thing works in the fakeroot context..

then… how did you set up the original 001-core?
Cause all 001-core contain the then most recent ca-certificates, right?

[Ed_P]

When/what exactly couldn't find the cfg file?

The beginning of the ISO boot process. The ISO and associated files/folders boot fine on my old notebook with a standard SSD drive. My Porteus 5.0rc3 ISO boots fine on both it and the M.2 SSD drive.

Added in 14 hours 50 minutes 36 seconds:



The Porteus 4.0 folder on the same hvme0n drive as the Porteus 5.0 folder.


My grub2 menu:

Code: Select all

     set linux_folder=/porteus4.0
     if [ -f /boot/syslinux/vmlinuz ]; then linux_folder=""; fi    # USB install
#    LXQT  MATE  OPENBOX  XFCE
     set iso=/ISOs/Porteus-CINNAMON-v4.0-x86_64.iso
#     set iso=/ISOs/Porteus-OPENBOX-v4.0-x86_64.iso
     set extramods="extramod="

menuentry " Porteus 4.0 ISO - AF'" --class slackware   --class icon-porteus  {

#     set boot_parms="volume=33 reboot=cold $extramods$linux_folder/Modules"
     set boot_parms="volume=33 reboot=cold $extramods$linux_folder/Modules;$linux_folder/modsavedat noload=save.dat;cinnamon"

     search -f $iso --set=root
     loopback loop $iso
     linux  (loop)/boot/syslinux/vmlinuz from=$iso $boot_parms
     initrd (loop)/boot/syslinux/initrd.xz
     }

It seems that Porteus 4.0's vmlinuz or initrd.xz doesn't support the new M.2 SSD drives.

Added in 1 hour 33 minutes 36 seconds:
The Porteus 4.0 system run on my old notebook.

Code: Select all

~#  uname -a
Linux porteus 4.16.3-porteus #1 SMP PREEMPT Sat Apr 21 12:42:52 Local time zone must be set-- x86_64 Intel(R) Core(TM) i3-6100U CPU @ 2.30GHz GenuineIntel GNU/Linux

~#  cat /etc/porteus/*
001-core.xzm:20180422
002-xorg.xzm:20180422
003-cinnamon.xzm:20180702
initrd.xz:20180311

ISO: /ISOs/Porteus-CINNAMON-v4.0-x86_64.iso

So what kernel(?) do I need to upgrade Porteus 4.0 to for NVMe drive support.

[fulalas]

Can you try a clean 'install' (i.e. just /boot and /porteus)?

[Ed_P]

I don't know how to boot an ISO using just /boot and /porteus. And I only install to USB drives.

Added in 12 minutes 1 second:
And this option didn't help.

blkid knows no NVME hard disks in rescue-shell

Added in 17 minutes 39 seconds:
Porteus 4.0 boots on the new notebook from a USB drive.

Code: Select all

~#  uname -a
Linux porteus 4.16.3-porteus #1 SMP PREEMPT Sat Apr 21 12:42:52 Local time zone must be set-- x86_64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz GenuineIntel GNU/Linux

~#  cat /etc/porteus/*
001-core.xzm:20180422
002-xorg.xzm:20180422
003-cinnamon.xzm:20180702
initrd.xz:20180311

~#  ls -l /mnt/live/memory/images
000-kernel.xzm : Apr 21 2018
001-core.xzm : Apr 22 2018
002-xorg.xzm : Apr 22 2018
003-cinnamon.xzm : Jul 15 2016
003-jinnamon-180702.xzm : Jul 15 2016
007-printing-x86_64-2018-02-23.xzm : Jan 21 2018

And on the new notebook it is lacking network and sound support. This system runs fine on my older Dell and Acer notebooks.

Added in 1 day 9 hours 18 minutes 33 seconds:
Copied the kernel 5.16.11 files from 5.0rc but they don't help the ISO booting problem. Will try the USB install tomorrow.

[Rava]

Network/WLAN issue with Porteus 4.0 i586

usually it works like a charm, but sometimes it does not.
using XFCE 4.12 I connect with the ModemManager icon - and when I open the icon menu showing me the connections - I see that there is some kind of "reset" - all seen WLANs vanish, only to be reset some seconds later. When I try again the same thing happens, like, 5 times in a row until finally I can connect to my WLAN and from then on it works like always.

Here is what /var/log/messages says in one such instance of "reset"

Code: Select all

Sep 15 13:11:12 porteus NetworkManager[772]: <info>  [1663240272.1065] device (w
lan0): state change: config -> failed (reason 'ssid-not-found', internal state '
managed')
Sep 15 13:11:12 porteus NetworkManager[772]: <info>  [1663240272.1085] manager: 
NetworkManager state is now CONNECTED_LOCAL
Sep 15 13:11:12 porteus NetworkManager[772]: <info>  [1663240272.1101] device (w
lan0): supplicant interface state: scanning -> disconnected
Sep 15 13:11:12 porteus NetworkManager[772]: <info>  [1663240272.1163] device (w
lan0): state change: failed -> disconnected (reason 'none', internal state 'mana
ged')
Sep 15 13:11:12 porteus NetworkManager[772]: <info>  [1663240272.1372] device (w
lan0): set-hw-addr: set MAC address to xx:xx:xx:xx:xx:xx (scanning)
Sep 15 13:11:12 porteus kernel: [44803.145822] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sep 15 13:11:12 porteus NetworkManager[772]: <info>  [1663240272.3949] device (wlan0): supplicant interface state: disconnected -> disabled
Sep 15 13:11:12 porteus NetworkManager[772]: <info>  [1663240272.3962] device (wlan0): supplicant interface state: disabled -> disconnected

Any ideas what can be the reason? Where does the "reason 'ssid-not-found' " come from?

The "CONNECTED_LOCAL" could be the LAN sharing where this i586 Port 4.0 shares its Internet/WLAN with the x86-64 Port 5.0 - see here about this: [Solved via Networkmanager] masquerading and sharing via iptables

[Rava]

Porteus 4.0 i586 XFCE Power manager / Switch screen off fails.
It's a laptop, and it's about its build in screen.

Sometimes my screen off fails. And by sometime I mean: when it fails it fails every time. If it not fails it usually never fails. The settings is like this:

I even changed the "sleep after 1 minutes" to "2" and back to one minute. Closed XFCE Power manager and reopened it and it looked like the screenshot. It still fails.