Porteus-v5.0x86_64_bugs reports

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
spa_time
White ninja
White ninja
Posts: 20
Joined: 29 Jun 2022, 06:39
Distribution: Porteus 5.1

Porteus-v5.0x86_64_bugs reports

Post#1 by spa_time » 06 Jul 2022, 19:03

All appreciations for the work team - Porteus 5.0 _i586 iso is ok but x86_64 iso give an error for 002-xorg module
Tried to replace from Porteus 5.0rc3 but same error appear when base modules are loading
The error is also for Porteus 5.0 xfce , lxde , gnome
Also Porteus 4.0 x86_64 is working
Perhaps this post may help the team...all the best

User avatar
Ed_P
Contributor
Contributor
Posts: 8341
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Porteus-v5.0x86_64_bugs reports

Post#2 by Ed_P » 06 Jul 2022, 22:11

spa_time wrote:
06 Jul 2022, 19:03
Perhaps this post may help the team...all the best
Posting what the error msg says would be helpful and the specs of the machine you're booting it on, cause not everyone is getting the error. :happy62:
Ed

User avatar
AcnapyxoB
Samurai
Samurai
Posts: 191
Joined: 24 Dec 2014, 10:15
Distribution: Porteus 5.01
Location: Planet Earth

Porteus-v5.0x86_64_bugs reports

Post#3 by AcnapyxoB » 07 Jul 2022, 11:27

Congratulations for new 5.0

I ran into a few problems:

1. Encrypted dat file container [solved for xfs]
Can create savefile.dat, but it is unusable.
If previously created is used (from Porteus 4.0) can't decrypt it in boot time.
Аlready discussed in 5.0rc3 topic:
viewtopic.php?p=83384#p83384
viewtopic.php?p=83412#p83412
It is partially solved by replacing initrd.zx (can read already created dat file).
Same with New initrd.xz and cheatcodes (boot parameters) for Porteus

Found that it works with xfs (does't work with ext2, ext4, and reiserfs)
thanks to babam

2. Samba
Problem using a shared NAS in local network (Windows shares also)
Тhis thread doesn't help:
viewtopic.php?p=83575#p83575
Tried with KDE, Cinnamon and XFCE.
Can see shares thru terminal:

Code: Select all

smbclient -L \\192.168.XX.XXX -N
guest@guest:~$ smbclient -L \\192.168.XX.XXX -N

        Sharename       Type      Comment
        ---------       ----      -------
        Cloud           Disk      
        Droidbox        Disk      
        IPC$            IPC       IPC Service ("")
Reconnecting with SMB1 for workgroup listing.

        Server               Comment
        ---------            -------

        Workgroup            Master
        ---------            -------
        WORKGROUP            NAS520
guest@guest:~$ smbclient //192.168.XXX.XXX/Cloud -N
tree connect failed: NT_STATUS_ACCESS_DENIED
3. OpenConnect - last and less important
I have a module for openconnect VPN I (use it for work Cisco AnyConnect) that contains this four packages:
which works successfully with XFCE and Cinnamon, but does not want to work with KDE (it says Missing VPN plugin)
Last edited by AcnapyxoB on 08 Jul 2022, 17:38, edited 6 times in total.
Porteus v5.01 KDE x86_64

spa_time
White ninja
White ninja
Posts: 20
Joined: 29 Jun 2022, 06:39
Distribution: Porteus 5.1

Porteus-v5.0x86_64_bugs reports

Post#4 by spa_time » 07 Jul 2022, 11:37

Ed_P wrote:
06 Jul 2022, 22:11
spa_time wrote:
06 Jul 2022, 19:03
Perhaps this post may help the team...all the best
Posting what the error msg says would be helpful and the specs of the machine you're booting it on, cause not everyone is getting the error. :happy62:
When Porteus 5 is loading ... 002-xorg module is corrupted message appear ... and is stopping ... I replace this module from Porteus 5 rc3 but
the problem remain ... possible is other base module ... I will try also on laptop ...
Desktop Computer is Dell Optiplex I5 ... I will make some shots with cellphone ...tnx for answer ... all the best ...
....................................
So I tested same usb live stick with Porteus 5.0 on laptop - and is working - but very strange situation... on Dell Optiplex I5 desktop the error appear on
sistem loading with the same usb stick...and also with lxde 5.0, mate 5.0 , isos ...anyway ... all my appreciation for team efforts ... all the best ...
Screenshot at https://filebin.net/9bg3mq919z6cmyvw
Last edited by spa_time on 08 Jul 2022, 08:17, edited 2 times in total.

User avatar
babam
Warlord
Warlord
Posts: 526
Joined: 16 Nov 2016, 10:30
Distribution: Porteus 5.0rc3 Xfce K6.1.1
Location: Rainy city

Porteus-v5.0x86_64_bugs reports

Post#5 by babam » 07 Jul 2022, 15:40

AcnapyxoB wrote:
07 Jul 2022, 11:27
Congratulations for new 5.0

I ran into a few problems:

1. Encrypted dat file container
Can create savefile.dat, but it is unusable.
If previously created is used (from Porteus 4.0) can't encrypt it in boot time.
Аlready discussed in 5.0rc3 topic:
viewtopic.php?p=83384#p83384
viewtopic.php?p=83412#p83412
It is partially solved by replacing initrd.zx (can read already created dat file).
Same with New initrd.xz and cheatcodes (boot parameters) for Porteus
Check this out Porteus Kernel Builder (Post by AcnapyxoB #86279)
Sorry, my English is bad.

tome
Contributor
Contributor
Posts: 675
Joined: 26 Jun 2013, 14:03
Distribution: x64 Openbox
Location: Russia is causing the immense damage to humanity
Contact:

Porteus-v5.0x86_64_bugs reports

Post#6 by tome » 07 Jul 2022, 16:10

You have mind and feelings. Be wise and clever.

User avatar
AcnapyxoB
Samurai
Samurai
Posts: 191
Joined: 24 Dec 2014, 10:15
Distribution: Porteus 5.01
Location: Planet Earth

Porteus-v5.0x86_64_bugs reports

Post#7 by AcnapyxoB » 07 Jul 2022, 16:29

babam wrote:
07 Jul 2022, 15:40
Check this out Porteus Kernel Builder (Post by AcnapyxoB #86279)
Yes, I confirm that encrypted dat file (which is used to save changes) works, but not creating one !
Porteus v5.01 KDE x86_64

User avatar
babam
Warlord
Warlord
Posts: 526
Joined: 16 Nov 2016, 10:30
Distribution: Porteus 5.0rc3 Xfce K6.1.1
Location: Rainy city

Porteus-v5.0x86_64_bugs reports

Post#8 by babam » 07 Jul 2022, 16:50

AcnapyxoB wrote:
07 Jul 2022, 16:29

Yes, I confirm that encrypted dat file (which is used to save changes) works, but not creating one !
I don't understand, so what's the problem with Porteus 5.0 and encrypted save.dat?
Sorry, my English is bad.

User avatar
AcnapyxoB
Samurai
Samurai
Posts: 191
Joined: 24 Dec 2014, 10:15
Distribution: Porteus 5.01
Location: Planet Earth

Porteus-v5.0x86_64_bugs reports

Post#9 by AcnapyxoB » 07 Jul 2022, 17:07

babam wrote:
07 Jul 2022, 16:50
I don't understand, so what's the problem with Porteus 5.0 and encrypted save.dat?
It has already been written about:
viewtopic.php?p=83384#p83384

screen during boot says:

Code: Select all

^ found encrypted .dat container
Enter passphrase for /dev/loop2:
^ checking /dev/mapper/cript for errors
sh: xfs: unknown operand
sh: ext: unknown operand
sh: rei: unknown operand
^ detected unsupported fs - skipping fsck
^ changes not writable, using memory instead
the problem is probably in the build script it worked with Porteus v4.0
Porteus v5.01 KDE x86_64

User avatar
babam
Warlord
Warlord
Posts: 526
Joined: 16 Nov 2016, 10:30
Distribution: Porteus 5.0rc3 Xfce K6.1.1
Location: Rainy city

Porteus-v5.0x86_64_bugs reports

Post#10 by babam » 07 Jul 2022, 17:25

AcnapyxoB wrote:
07 Jul 2022, 17:07


screen during boot says:

Code: Select all

^ found encrypted .dat container
Enter passphrase for /dev/loop2:
^ checking /dev/mapper/cript for errors
sh: xfs: unknown operand
sh: ext: unknown operand
sh: rei: unknown operand
^ detected unsupported fs - skipping fsck
^ changes not writable, using memory instead
Does the encrypted container work on 5.0rc3?
Sorry, my English is bad.

User avatar
AcnapyxoB
Samurai
Samurai
Posts: 191
Joined: 24 Dec 2014, 10:15
Distribution: Porteus 5.01
Location: Planet Earth

Porteus-v5.0x86_64_bugs reports

Post#11 by AcnapyxoB » 07 Jul 2022, 17:30

babam wrote:
07 Jul 2022, 17:25
Does the encrypted container work on 5.0rc3?
If it is created with Porteus 4.0 yes.

Sorry!
I'm just using the release of the new Porteus v5.0 to look for a solution to an old problem!
It's not that important, I just want things to get better :beer:
Porteus v5.01 KDE x86_64

User avatar
babam
Warlord
Warlord
Posts: 526
Joined: 16 Nov 2016, 10:30
Distribution: Porteus 5.0rc3 Xfce K6.1.1
Location: Rainy city

Porteus-v5.0x86_64_bugs reports

Post#12 by babam » 07 Jul 2022, 18:38

AcnapyxoB wrote:
07 Jul 2022, 17:30

If it is created with Porteus 4.0 yes.

Is it the same encrypted container? on the same encrypted container doesn't work on Porteus 5.0 but works on 5.0rc3?
Sorry, my English is bad.

User avatar
AcnapyxoB
Samurai
Samurai
Posts: 191
Joined: 24 Dec 2014, 10:15
Distribution: Porteus 5.01
Location: Planet Earth

Porteus-v5.0x86_64_bugs reports

Post#13 by AcnapyxoB » 07 Jul 2022, 19:01

babam wrote:
07 Jul 2022, 18:38
Is it the same encrypted container? on the same encrypted container doesn't work on Porteus 5.0 but works on 5.0rc3?
I've said it several times - .dat file works with Porteus 4.0, 5.0rc3 and 5.0, the script that creates the container doesn't work on 5.0rc3 and 5.0 !?
You need to use an old Porteus version (4.0) to create it.
Last edited by AcnapyxoB on 08 Jul 2022, 06:52, edited 1 time in total.
Porteus v5.01 KDE x86_64

User avatar
babam
Warlord
Warlord
Posts: 526
Joined: 16 Nov 2016, 10:30
Distribution: Porteus 5.0rc3 Xfce K6.1.1
Location: Rainy city

Porteus-v5.0x86_64_bugs reports

Post#14 by babam » 07 Jul 2022, 19:40

AcnapyxoB wrote:
07 Jul 2022, 19:01

You need to use an old Porteus version (4.0) to create it.
old script was shel script, the new one is python
Ok I understand, the problem is with the Savefile Manager (/opt/porteus-scripts/make-changes).

I've never used Savefile Manager, I created a container manually using the terminal.
Last edited by babam on 07 Jul 2022, 21:10, edited 1 time in total.
Sorry, my English is bad.

sos
White ninja
White ninja
Posts: 4
Joined: 07 Jul 2022, 19:37
Distribution: x86_64 XFCE

Porteus-v5.0x86_64_bugs reports

Post#15 by sos » 07 Jul 2022, 20:09

Noticed that the cheat code login=root no longer seems to work. It was fine in 5.0rc3! This is with XFCE.
Specifically using as in: APPEND noauto login=root libata.force=1.00:disable which worked fine before.
Just wondering if this is by design or something got broken.

Post Reply