ArchLinux packages manager for Porteus

Here is a place for your projects which are not officially supported by the Porteus Team. For example: your own kernel patched with extra features; desktops not included in the standard ISO like Gnome; base modules that are different than the standard ISO, etc...
neko
DEV Team
DEV Team
Posts: 989
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

ArchLinux packages manager for Porteus

Post#316 by neko » 26 Nov 2017, 06:34

NEW example of Japanese locale ISOs that were created by "APorteus ISO builder" were updated.

Please refer to ArchLinux packages manager for Porteus (Post by neko #50011)


Thanks.

neko
DEV Team
DEV Team
Posts: 989
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

ArchLinux packages manager for Porteus

Post#317 by neko » 27 Nov 2017, 08:17

NEW example of Russia locale ISO that was created by "APorteus ISO builder" were updated.

Please refer to ArchLinux packages manager for Porteus (Post by neko #49911)


Thanks.

ddelma
Ronin
Ronin
Posts: 2
Joined: 06 Nov 2017, 09:04
Distribution: elementary os

ArchLinux packages manager for Porteus

Post#318 by ddelma » 28 Nov 2017, 18:09

APorteus-BUDGIE won't start the DE
I downloaded APorteus-BUDGIE-v17.11.21-x86_64.iso and burned it on a USB flash drive. Every thing is fine included md5sum check. Booting begin well until it it throw me this: "You are in emergency mode...." Image
In the previous page I noticed a double slash before 'rootcopy'. "copying content of /mnt/sda1/porteus//rootcopy directory"
what should I do to enjoy Budgie DE on Aporteus-Budgie

I am Puppy Linux forma user and lastly elementary OS. I now discovered Porteus and I am very excited about Aporteus.

neko
DEV Team
DEV Team
Posts: 989
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

ArchLinux packages manager for Porteus

Post#319 by neko » 29 Nov 2017, 07:08

@ddelma
Thank you for your interest to APorteus.

["You are in emergency mode...." issue]
I guess that after intram starting systemd was fault.
Please try following steps.

1.analyze the systemd process by run level 3.
(1) add cheatcode "3" into your boot config.
(2) If boot will be OK and login window will appear,
login: guest
password: guest
% sudo update-cache
password: toor
[y/n]: n
% startx


2.analyze boot device by changing the storage of ISO.
I guess that the content of ISO was expanded in USB (/mnt/sda1).

Code: Select all

/mnt/sda1/USB_INSTALLATION.txt

/mnt/sda1/.disk/info

/mnt/sda1/EFI/boot/bootx64.efi
/mnt/sda1/EFI/boot/grub.cfg

/mnt/sda1/boot/Porteus-installer-for-Linux.com
/mnt/sda1/boot/Porteus-installer-for-Windows.exe

/mnt/sda1/boot/docs/GNU_GPL
/mnt/sda1/boot/docs/License.txt
/mnt/sda1/boot/docs/cheatcodes-ja.txt
/mnt/sda1/boot/docs/cheatcodes.txt
/mnt/sda1/boot/docs/install.txt
/mnt/sda1/boot/docs/requirements.txt

/mnt/sda1/boot/syslinux/chain.c32
/mnt/sda1/boot/syslinux/extlinux.conf
/mnt/sda1/boot/syslinux/initrd.xz
/mnt/sda1/boot/syslinux/isolinux.bin
/mnt/sda1/boot/syslinux/isolinux.boot
/mnt/sda1/boot/syslinux/isolinux.cfg
/mnt/sda1/boot/syslinux/lilo.conf
/mnt/sda1/boot/syslinux/plpbt
/mnt/sda1/boot/syslinux/porteus.cfg
/mnt/sda1/boot/syslinux/porteus.png
/mnt/sda1/boot/syslinux/syslinux.cfg
/mnt/sda1/boot/syslinux/vesamenu.c32
/mnt/sda1/boot/syslinux/vmlinuz

/mnt/sda1/porteus/kernel-v4.14.1-1-x86_64.sgn
/mnt/sda1/porteus/make_iso.sh

/mnt/sda1/porteus/base/000-kernel.xzm
/mnt/sda1/porteus/base/001-core.xzm
/mnt/sda1/porteus/base/001-z.core.xzm
/mnt/sda1/porteus/base/002-xorg.xzm
/mnt/sda1/porteus/base/002-z.xorg.xzm
/mnt/sda1/porteus/base/003-budgie.xzm
/mnt/sda1/porteus/base/003-z.budgie.xzm

/mnt/sda1/porteus/modules/
/mnt/sda1/porteus/optional/
/mnt/sda1/porteus/rootcopy/
(1) set APorteus-BUDGIE-v17.11.21-x86_64.iso in the USB(/mnt/sda1/)
/mnt/sda1/APorteus-BUDGIE-v17.11.21-x86_64.iso
(2) change boot config by inserting cheatcode as follow.
from=/APorteus-BUDGIE-v17.11.21-x86_64.iso
(3) boot by new config

If you will try, Would you tell me the results ?
(What file system is USB(/dev/sda1) ?)


Thanks.
-------------------------------------------------------------
@all
"Integrated Simple Package Management tool" was updated to 17.11.28.

"mkdevel" command was updated to creating devel.xzm that includes "libelf&openssl" headers
in order to build kernel v4.15-rc line.

Please refer to ArchLinux packages manager for Porteus (Post by neko #36687)


Thanks.

raja
Black ninja
Black ninja
Posts: 64
Joined: 02 May 2017, 09:51
Distribution: v3.2.2-32bit and v3.2.2-64 bit
Location: Chennai,India

ArchLinux packages manager for Porteus

Post#320 by raja » 30 Nov 2017, 10:58

neko, here is the "shutdown" script used by TM (copy right owner), to overcome the 'dead end' faced by systemd.
#!/bin/sh
# Shutdown script for initramfs. It's automatically started by
# systemd (if you use it) on shutdown, no need for any tweaks.
# Purpose of this script is to unmount everything cleanly.
#
# Author: Tomas M <http://www.linux-live.org/>
#

. /lib/config
. /lib/livekitlib

debug_start

debug_log "Entering shutdown procedures of Linux Live Kit"
debug_log "Called with arguments: " "$*"

# if debug is enabled, run shell now
debug_shell

detach_free_loops()
{
losetup | cut -d : -f 1 | xargs -r -n 1 losetup -d
}

# $1=dir
umount_all()
{
tac /proc/mounts | cut -d " " -f 2 | grep ^$1 | while read LINE; do
umount $LINE 2>/dev/null
done
}

# Update devs so we are aware of all active /dev/loop* files.
# Detach loop devices which are no longer used
debug_log "- Detaching loops"
mdev -s
detach_free_loops

# do it the dirty way, simply try to umount everything to get rid of most mounts
debug_log "- Unmounting submounts of union"
umount_all /oldroot

# free aufs of /run mount, and umount aufs
debug_log "- Unmounting union itself"
mkdir /run2
mount --move /oldroot/run /run2
umount /oldroot

# remember from which device we are started, so we can eject it later
DEVICE="$(cat /proc/mounts | grep /memory/data | grep /dev/ | cut -d " " -f 1)"

debug_log "- going through several cycles of umounts to clear everything left"
umount_all /run2
detach_free_loops
umount_all /run2
detach_free_loops
umount_all /run2

# eject cdrom device if we were running from it
for i in $(cat /proc/sys/dev/cdrom/info | grep name); do
if [ "$DEVICE" = "/dev/$i" ]; then
echo "[ OK ] Attemptiong to eject /dev/$i..."
eject /dev/$i
echo "[ OK ] CD/DVD tray will close in 6 seconds..."
sleep 6
eject -t /dev/$i
fi
done

debug_shell

debug_log $1 -f
$1 -f

debug_log reboot -f
reboot -f

echo We should never reach so far. Something is totally fucked up.
echo Here you have a shell, to experiment with the universe.
/bin/sh
You can modify to suit porteus init script. wishing you all the best.

neko
DEV Team
DEV Team
Posts: 989
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

ArchLinux packages manager for Porteus

Post#321 by neko » 30 Nov 2017, 13:07

@raja
Thank you for your advice.
I am studying it.
Please refer to New Slax is Comming ! (Post by neko #60257)

If you have a time, please answer following question.
ArchLinux packages manager for Porteus (Post by neko #60045)
----------------
1. firmware for ath10k
You have already fixed this problem by yourself.
It is very good.
The reason is that Porteus has the restrict to include many firmwares in order to reduce ISO size.
In opposition to that "UBUNTU" includes many firmwares.
Therefor a few Porteus users need to add firmware by themself.

Would you tell me what ath10k firmware you used more exactly ?
---------------

Thanks.

ddelma
Ronin
Ronin
Posts: 2
Joined: 06 Nov 2017, 09:04
Distribution: elementary os

ArchLinux packages manager for Porteus

Post#322 by ddelma » 30 Nov 2017, 15:22

Thank you for your fast answer. I tried suggested steps.
Methode 1. The login window didn't appear, but the prompt. when logged as root and execute xstart, it tries to open but falls back into the prompt. I could read "xauth: file /root/.Xauthority does not exist..." I exported the /var/log/Xorg.0.log. Here are its (EE)
[ 70.870] (EE) dbus-core: error connecting to system bus: org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory)
[ 72.134] (EE) dbus-core: error connecting to system bus: org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory)

Methode 2. It's the same story. I should mention that I burned the drive with the Porteus 'create USB drive' tool with default options. Afterward I burn it with dd and the same result happened. The xfce version is no exception

neko
DEV Team
DEV Team
Posts: 989
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

ArchLinux packages manager for Porteus

Post#323 by neko » 03 Dec 2017, 13:49

@ddelma
Excuse me for my delayed response.

==========
From your first report, I guessed as follow.
After initram, starting systemd was fault.
The reason was that mounting some modules that are included in ISO were missing.
And one of this reason was that your USB did not include the missing modules.
Or another reason was that the module in USB were broken.

Therefor I requested you to try booting on run level 3.
---->
Your result was that login message did not appear.

Code: Select all

[ 70.870] (EE) dbus-core: error connecting to system bus: org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory)
One more, I requested you to try booting from ISO.
---->
Same result as above.

Code: Select all

[ 70.870] (EE) dbus-core: error connecting to system bus: org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory)
This error was reported.
https://bugs.launchpad.net/ubuntu/+sour ... bug/811441


==========
From your recent report, I guessed as follow.
Maybe, APorteus has some bugs.
Now, it is difficult for me to fix the issue.

But, if you have time, please one more try another boot method.

APorteus can be booted from ISO directly by using "from=" cheatcode (boot paramater).
It is better to use linux file system (ext3, ext4) instead of Windowns file system (FAT,NTFS).

set APorteus-BUDGIE-v17.11.21-x86_64.iso
in /path directory of ext3 partition (uuid "NNNNNNNN-NNNN-NNNN-NNNN-NNNNNNNNNNNN")

If Your boot tool is EFI/grub2, boot config is

Code: Select all

menuentry "BUDGIE" {
set uuid="NNNNNNNN-NNNN-NNNN-NNNN-NNNNNNNNNNNN"
search --no-floppy --fs-uuid --set=root $uuid
set ISO="/path/APorteus-BUDGIE-v17.11.21-x86_64.iso"
linux (loop)/boot/syslinux/vmlinuz from=UUID:$uuid/$ISO copy2ram reboot=force retry 
initrd (loop)/boot/syslinux/initrd.xz
}
If Your boot tool is syslinux/extlinux, boot config is

Code: Select all

LABEL budgie
MENU LABEL budgie
KERNEL /getpath/vmlinuz
APPEND initrd=/getpath/initrd.xz from=UUID:NNNNNNNN-NNNN-NNNN-NNNN-NNNNNNNNNNNN/path/APorteus-BUDGIE-v17.11.21-x86_64.iso copy2ram reboot=force retry 
In /getpath of syslinux/extlinux setting partition, vmlinuz & initrd.xz are set.
vmlinuz & initrd.xz are extracted from the ISO.


Thanks.

raja
Black ninja
Black ninja
Posts: 64
Joined: 02 May 2017, 09:51
Distribution: v3.2.2-32bit and v3.2.2-64 bit
Location: Chennai,India

ArchLinux packages manager for Porteus

Post#324 by raja » 05 Dec 2017, 08:56

Neko, I somehow missed your query on firmware-ath10k. Sorry about that. The Laptop at home which uses ath10k wireless card is a shared one, and I try it only occasionally. I use 32 bit old laptop, normally.

Since the dmesg was not pin pointing on a particular 10k firmware. I, inserted the whole ath10k folder, around 5mbs, from porteus.

On the issue of webcam listed as 'keyboard'.- I think it surfaced only from Kernel version 4.13. Cheese ,shows my face in kernel 4.12.8.

New Kernels can introduce ,'new problems'.

I tried, your 32 bit budgie and FVWM (with new kernel), with kernel 4.4.76( old laptop does not like new kernels!). I could boot into only 'root' after a struggle. Everything except 'wireless network' in order. I get 'device not ready' error. kernel driver and firmware are loaded.

I think, something is powering off 'wifi (aeroplane mode) during boot. rfkill is not listing the device.

I will try again and seek your help later.

neko
DEV Team
DEV Team
Posts: 989
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

ArchLinux packages manager for Porteus

Post#325 by neko » 05 Dec 2017, 10:50

@raja
Thank you for your report.

Now, "Porteus Kernel Builder" can copy firmwares from packages.
But these pacakges don't have a full set firmware.
If someone needs a firmware for his PC, he must search it in network and then introduce into his kernel.
If I know a firmware name that you need, I intended to introduce it into packages pool.

Bytheway, the example of the latest longterm 4.9 version of the Linux kernel 4.9.66 was uploaded.
Please refer to Porteus Kernel Builder (Post by neko #60849)
This exapmle includes "copied firmware from packages".

Thanks.

raja
Black ninja
Black ninja
Posts: 64
Joined: 02 May 2017, 09:51
Distribution: v3.2.2-32bit and v3.2.2-64 bit
Location: Chennai,India

ArchLinux packages manager for Porteus

Post#326 by raja » 06 Dec 2017, 09:17

Neko, Can you please make a 32 bit version ISO with FVWM - DE, but with Kernel v4.4.104? Thanks.

neko
DEV Team
DEV Team
Posts: 989
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

ArchLinux packages manager for Porteus

Post#327 by neko » 06 Dec 2017, 10:47

1. @raja
"Neko, Can you please make a 32 bit version ISO with FVWM - DE, but with Kernel v4.4.104? Thanks."

Yes, I can.
Please give me time.
("building Kernel v4.4.104", "creating ISO" and "uploading it" need some time).

Thanks.


2. @all
NEW example of ISOs that were created by "APorteus ISO builder" were uploaded.

====[64 BIT]====
Language: English (locale C)
kernel version: 64Bit 4.9.67
Packages version: the latest version at the time of creating ISO (2017.12.05).

Multiple ISO and 13 application modules are uploaded.
This multiple ISO includes FVWM, OPENBOX, LXDE, E16, XFCE, and BUDGIE desktops.

====[32 BIT]====
Language: English (locale C)
kernel version: 32Bit 4.9.67
Packages version: the latest version at the time of creating ISO (2017.12.05).

Multiple ISO and 13 application modules are uploaded.
This multiple ISO includes FVWM, OPENBOX, LXDE, E16, XFCE, and BUDGIE desktops.


Refer to ArchLinux packages manager for Porteus (Post by neko #49091)


Thanks.

neko
DEV Team
DEV Team
Posts: 989
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

ArchLinux packages manager for Porteus

Post#328 by neko » 06 Dec 2017, 15:34

@raja
32bit kernel 4.4.104, FVWM desktop APorteus
APorteus-FVWM-v17.12.05-i486.iso (297 M)
http://www.mediafire.com/file/0e28agi5i ... 5-i486.iso
md5sum: 3a795a9d2b534c5a5a600a7dcaad970f APorteus-FVWM-v17.12.05-i486.iso


Note 1:
This ISO couldn't be booted in my PC.
Maybe, kernel 4.4.104 is mismatch with my PC.

But kernel 4.9.67 is match with my PC.
You can test 32 bit FVWM APorteus with kernel 4.9.67 by using APorteus-MULT-v17.12.05-i486.iso.
Please refer to ArchLinux packages manager for Porteus (Post by neko #49091)


Note 2:
This is 32 Bit kernel version 4.4.104 build example.
v4.4.104-32.tar.xz (35 M)
http://www.mediafire.com/file/418d3yns8 ... -32.tar.xz
md5sum: a287dd0c0d0f924ca861f5a166848653 v4.4.104-32.tar.xz



Thanks.

neko
DEV Team
DEV Team
Posts: 989
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

ArchLinux packages manager for Porteus

Post#329 by neko » 07 Dec 2017, 02:41

NEW example of German locale ISO that was created by "APorteus ISO builder" was updated.

Please refer to ArchLinux packages manager for Porteus (Post by neko #49970)


Thanks.

raja
Black ninja
Black ninja
Posts: 64
Joined: 02 May 2017, 09:51
Distribution: v3.2.2-32bit and v3.2.2-64 bit
Location: Chennai,India

ArchLinux packages manager for Porteus

Post#330 by raja » 07 Dec 2017, 07:24

Neko, you are too fast, amazing to see, outputs like in an automated mass producing facility.

Your offering, Kernel 4.4.104 worked like a charm in my old Laptop. FVWM, lean at 180 mb memory usage ,when compared to stiff 700 mb for Gnome/Budgie. m/c runs as fast as in Porteus 3.2.2.
[ 29.156] Build Operating System: Linux 4.13.5-1-ARCH i686
[ 29.156] Current Operating System: Linux porteus 4.4.104-porteus #1 SMP PREEMPT Wed Dec 6 18:46:41 UTC 2017 i686

Video copy Benchmarking as good as in Porteus.

29.688] (--) CHROME(0): Timed MMX YUV420 copy... 1030272. Throughput: 921.3 MiB/s.
Many thanks.

Post Reply