Page 1 of 1

Porteus very slow after clean install on

Posted: 03 May 2020, 18:49
by vanAuss
Hello everyone,
I started Porteus first time with FAT32 format. Everything was very fast. Boot and shut down was super quick. And now i have USB with ext4 format for making changes saving. I use only Firefox with couple of tabs (max 8) - only reading this forum for learning. Whole systems lags, sometimes freeze for couple of seconds, especially when i trying listen music with from youtube or some streamed radio. Boot and especially shut down takes very long time than before... I dont have these problem before with fat32 (iam not sure, if it with that, but is only things was changed). Iam sure i have good hardware for running, see:
Linux porteus 4.16.3-porteus #1 SMP PREEMPT
Sat Apr 21 12:42:52 Local time zone must be set--
x86_64 AMD FX(tm)-8300 Eight-Core Processor AuthenticAMD GNU/Linux

Can I try to fix?

Thanks in advance!

vanAuss

Porteus very slow after clean install on

Posted: 03 May 2020, 20:08
by donald
Hi vanAuss

I prefer an ext2 filesystem on (usb) flash drives.
And also to point directly to the device, because sdXN as an identifier is not static.
It depends on how many devices are plugged-in.
The UUID is uniq.

Example
My usb-drive/boot/syslinux/porteus.cfg contains this:

APPEND from=UUID:97040ed6-6566-4bfc changes=UUID:97040ed6-6566-4bfc/porteus

How to get the UUID

Code: Select all

root@porteus:/# blkid
................
/dev/sdXN: UUID="97040ed6-6566-4bfc" TYPE="ext2" PARTUUID="342ed593-01"
...............
XN = subtitute with your device.

Porteus very slow after clean install on

Posted: 03 May 2020, 20:26
by vanAuss
donald wrote:
03 May 2020, 20:08
Hi vanAuss

I prefer an ext2 filesystem on (usb) flash drives.
And also to point directly to the device, because sdXN as an identifier is not static.
It depends on how many devices are plugged-in.
The UUID is uniq.

Example
My usb-drive/boot/syslinux/porteus.cfg contains this:

APPEND from=UUID:97040ed6-6566-4bfc changes=UUID:97040ed6-6566-4bfc/porteus

How to get the UUID

Code: Select all

root@porteus:/# blkid
................
/dev/sdXN: UUID="97040ed6-6566-4bfc" TYPE="ext2" PARTUUID="342ed593-01"
...............
XN = subtitute with your device.
Thank you for answer. I will in future use my USB on many computers, not only one where are testing Porteus now.
If ext2 is better i can make format for this. There is no problem for me...

Got this

Code: Select all

root@porteus:/home/guest# blkid
/dev/sda1: UUID="f89b6d8b-2f70-424c-b259-fdf4424892bc" TYPE="ext4" PARTUUID="cd502608-2050-4851-9401-e32c9e4a857e"
/dev/sdb1: UUID="1a542036-eb04-4642-8222-dbcaea81b667" TYPE="ext4" PARTUUID="09c12122-01"
/dev/sdc1: UUID="028edfa0-282e-48c4-8516-3c56e03b8f6d" TYPE="ext4" PARTUUID="030679e7-01"
/dev/sdd1: LABEL="PORTEUS" UUID="315f9274-b520-d601-301b-9274b520d601" TYPE="ext4" PARTUUID="c3072e18-01"
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
and my USB is with label PORTEUS

Porteus very slow after clean install on

Posted: 03 May 2020, 20:31
by Ed_P
With an ext4 filesystem I believe it is a journallng system and Porteus changes are written to it as they occur and browsers create lots of changes as they are used and USB drives are not the fastest. With a FAT32 filesystem changes are written to a porteussave.dat file and with that changes can be held until shutdown before being written using the changes=EXIT option. Maybe that's what you had before vanAuss.

Also if you boot the USB drive on EFI systems they won't recognize the ext4, or ext2, filesystem.

Porteus very slow after clean install on

Posted: 03 May 2020, 20:59
by vanAuss
Ok Ed you recommend to switch back to FAT32? Or buy new faster USB stick can help?

Many thanks for help

Porteus very slow after clean install on

Posted: 03 May 2020, 22:13
by Ed_P
Well, you did say
vanAuss wrote:
03 May 2020, 18:49
I started Porteus first time with FAT32 format. Everything was very fast. Boot and shut down was super quick.
Was that on a USB stick?

Journeling filesystems, ext4 and NTFS, were designed for hard drives and don't do well on flash drives even though they have no moving parts. For compatibility with multiple systems; Windows, Macs, Android, etc FAT32 is pretty much universal. For BIOS and EFI systems FAT32 wins again. FAT32 has limitations, the 32 GB drive size and the 4 GB file size.

So, you have to decide what's important to you and fits your needs.

Porteus very slow after clean install on

Posted: 04 May 2020, 04:18
by ncmprhnsbl
you can use changes=EXIT:<pathORuuid> with ext format too.. for the best of both worlds(POSIX and no journalling) try ext2 : don't need a .dat container and less wear on the flash drive..
changes=EXIT: might make shutdown a bit slower.. another thing for general speedup is copy2ram cheatcode if you have plenty of RAM, that is..although that lengthens boot time a little..

Porteus very slow after clean install on

Posted: 04 May 2020, 10:33
by vanAuss
Ed_P wrote:
03 May 2020, 22:13
Well, you did say
vanAuss wrote:
03 May 2020, 18:49
I started Porteus first time with FAT32 format. Everything was very fast. Boot and shut down was super quick.
Was that on a USB stick?

Journeling filesystems, ext4 and NTFS, were designed for hard drives and don't do well on flash drives even though they have no moving parts. For compatibility with multiple systems; Windows, Macs, Android, etc FAT32 is pretty much universal. For BIOS and EFI systems FAT32 wins again. FAT32 has limitations, the 32 GB drive size and the 4 GB file size.

So, you have to decide what's important to you and fits your needs.
I tried with FAT32 and was little better but too slow. FAT32 with copy ram run great, but i loose all changes for next reboot, or ? When i was end it in copy2ram i loose everything (wifi password too) But if i start system with copy2ram it don't save the last changes, or ?
ncmprhnsbl wrote:
04 May 2020, 04:18
you can use changes=EXIT:<pathORuuid> with ext format too.. for the best of both worlds(POSIX and no journalling) try ext2 : don't need a .dat container and less wear on the flash drive..
changes=EXIT: might make shutdown a bit slower.. another thing for general speedup is copy2ram cheatcode if you have plenty of RAM, that is..although that lengthens boot time a little..
Thanks for answer. Tried with ext2 but its too slow. But not jet tried with copy2ram. But if i start system with copy2ram it dont save the last changes, or ?

Porteus very slow after clean install on

Posted: 04 May 2020, 11:49
by ncmprhnsbl
vanAuss wrote:
04 May 2020, 10:33
But if i start system with copy2ram it dont save the last changes, or ?
i can see where the confusion is: there's a boot entry "copy2ram" .. but copy2ram is also just a cheatcode you can add to the APPEND line of any boot entry.. eg.

Code: Select all

LABEL GRAPHICAL
MENU LABEL Graphics mode
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND changes=EXIT:/porteus copy2ram

Porteus very slow after clean install on

Posted: 04 May 2020, 12:16
by vanAuss
ncmprhnsbl wrote:
04 May 2020, 11:49
vanAuss wrote:
04 May 2020, 10:33
But if i start system with copy2ram it dont save the last changes, or ?
i can see where the confusion is: there's a boot entry "copy2ram" .. but copy2ram is also just a cheatcode you can add to the APPEND line of any boot entry.. eg.

Code: Select all

LABEL GRAPHICAL
MENU LABEL Graphics mode
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND changes=EXIT:/porteus copy2ram
Aaah, thank you soo much. Its work great now! :)

But have some more issues now

1) I don't hear music from my headphone (if i run from RAM). Only from HDA Nvidia Digital stereo (HDMI3) - my monitor
2) For experiment try to install Atom editor, everything work fine and quick, but when i try save my on my USB stick i cannot save it, because i don't have permission. Its available to solve it ?

Thanks in advance!

Porteus very slow after clean install on

Posted: 04 May 2020, 12:34
by vanAuss
Answer for self
1) Headphones - work after some while and must for many times change the output by hand in icon
2) Update permision of file for folder (work now)