3.2.2 migration to 4.0 problem.

New features which should be implemented in Porteus; suggestions are welcome. All questions or problems with testing releases (alpha, beta, or rc) should go in their relevant thread here, rather than the Bug Reports section.
User avatar
Ed_P
Contributor
Contributor
Posts: 3599
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

3.2.2 migration to 4.0 problem.

Post#31 by Ed_P » 14 Dec 2017, 00:05

The /etc/NetworkManager/system-connections/* and /var/run/NetworkManager/* files work with LXQT.

-update-

And XFCE and LXDE.
Ed

User avatar
wread
Module Guard
Module Guard
Posts: 1131
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v4.0-kde-64 bits
Location: Santo Domingo
Contact:

3.2.2 migration to 4.0 problem.

Post#32 by wread » 14 Dec 2017, 10:55

@EdP
You definitely didn't read my last post! Do as I say and you won't miss it!
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!

User avatar
Ed_P
Contributor
Contributor
Posts: 3599
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

3.2.2 migration to 4.0 problem.

Post#33 by Ed_P » 14 Dec 2017, 16:09

:D I did read your last post wread but I boot the ISOs I don't install them so removing pieces is a bit more work.
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 5757
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

3.2.2 migration to 4.0 problem.

Post#34 by brokenman » 15 Dec 2017, 01:20

wread wrote:
13 Dec 2017, 21:27
Try taking out NetworkManager and ModemManager of 001-core. Traditionally they both belong in 002-xorg. The 001-core module includes the pns-tool from fanthom, so one can connect to the net easily in text mode; you don't need NetworkManager. That way you will definitely find out if NM is the cause of the trouble...
The pns-tool is there for historic reasons but is not needed. NetworkManager now contains nmtui for connections even in text mode. The problem is most certainly nothing to do with NetworkManager being in 001. The problem is not even NetworkManager. The problem only appears when a folder is saved, meaning that nothing in 001 is the problem, but rather the top level aufs branch is causing the problem, something being saved after the 001 module is loaded. If you suspect something different, please do what you suggest and post back real results but I highly doubt the theory.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
wread
Module Guard
Module Guard
Posts: 1131
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v4.0-kde-64 bits
Location: Santo Domingo
Contact:

3.2.2 migration to 4.0 problem.

Post#35 by wread » 15 Dec 2017, 20:21

@brokenmann
My work at the uni is research. You must discard possibilities to proof whatever you suspect! Right?
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!

User avatar
wread
Module Guard
Module Guard
Posts: 1131
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v4.0-kde-64 bits
Location: Santo Domingo
Contact:

3.2.2 migration to 4.0 problem.

Post#36 by wread » 16 Dec 2017, 01:14

@Ed_P
You don't have to be a guru to take out NetworkManager out of memory after the iso is loaded...
you just do in a console, as root:

root@porteus:~# removepkg NetworkManager-1.10.0-x86_64-2

That's all :)
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!

User avatar
Ed_P
Contributor
Contributor
Posts: 3599
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

3.2.2 migration to 4.0 problem.

Post#37 by Ed_P » 16 Dec 2017, 04:39

But the problem wread occurs when booting not after I have booted. After removing the networkmanager I would have to rebuild the ISO to test a reboot. And the problem seems to be limited to only 1 of the 4 ISOs I have tested. 3.2.2 migration to 4.0 problem. (Post by Ed_P #61082)
Ed

M. Eerie
Black ninja
Black ninja
Posts: 62
Joined: 31 Aug 2017, 21:18
Distribution: APorteus BUDGIE x64

3.2.2 migration to 4.0 problem.

Post#38 by M. Eerie » 16 Dec 2017, 14:45

I've been trying the Porteus 4.0 rc1 and I must say it's amazing. Impressive job. Fast and straightforward. Has all of the convenient needs.

One thing I've found that maybe should be modified: MD5 hash in right click menu says: 'Calculate MD5' (or something similar), when in fact, it tries to perform a MD5 check against a previous value. A bit confusing.

Actually would be nice a Calculate MD5 option.

Code: Select all

$(md5sum %f)
Thanks for your work!

:)

User avatar
brokenman
Site Admin
Site Admin
Posts: 5757
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

3.2.2 migration to 4.0 problem.

Post#39 by brokenman » 16 Dec 2017, 23:22

You must discard possibilities to proof whatever you suspect! Right?
Absolutely. Please do it.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
wread
Module Guard
Module Guard
Posts: 1131
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v4.0-kde-64 bits
Location: Santo Domingo
Contact:

3.2.2 migration to 4.0 problem.

Post#40 by wread » 17 Dec 2017, 00:34

@brokenman
Where is the iso? i will test it, of course!
It will be a pleasure to find out what is on..
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!

M. Eerie
Black ninja
Black ninja
Posts: 62
Joined: 31 Aug 2017, 21:18
Distribution: APorteus BUDGIE x64

3.2.2 migration to 4.0 problem.

Post#41 by M. Eerie » 17 Dec 2017, 09:30


User avatar
wread
Module Guard
Module Guard
Posts: 1131
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v4.0-kde-64 bits
Location: Santo Domingo
Contact:

3.2.2 migration to 4.0 problem.

Post#42 by wread » 17 Dec 2017, 13:01

I downloaded Cinnamon, copied to a USB and ran it: beautiful! :celebrate3:
Somehow it is working too slow...I will investigate deeper to see what may be wrong...

Cheers!
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!

fulalas
DEV Team
DEV Team
Posts: 960
Joined: 26 Oct 2016, 15:34
Distribution: Porteus
Location: Brazil

3.2.2 migration to 4.0 problem.

Post#43 by fulalas » 18 Dec 2017, 03:11

@wread, can you be more specific regarding the performance? Like, your machine specs, what exactly is slow and how slow, etc.

Jack
Contributor
Contributor
Posts: 1452
Joined: 09 Aug 2013, 14:25
Distribution: Porteus 4.0rc4 My Mate 64 bit
Location: USA

3.2.2 migration to 4.0 problem.

Post#44 by Jack » 18 Dec 2017, 03:44

fulalas wrote:
18 Dec 2017, 03:11
@wread, can you be more specific regarding the performance? Like, your machine specs, what exactly is slow and how slow, etc.
When I try jssouza Mate about a month ago it ran slow to and the more I did the slower it got. Here is my spec. https://www.cnet.com/products/acer-aspi ... nal/specs/
I just like Slackware because I think it teach you about Linux to build packages where Ubuntu is like Windows you just install programs you want.

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

3.2.2 migration to 4.0 problem.

Post#45 by raja » 18 Dec 2017, 09:16

Had a first look at porteus4.0-cinnamon.

Fastest Porteus boot till now. 9.5 seconds.
[8.549] Build Operating System: Slackware 14.2 Slackware Linux Project
[8.549] Current Operating System: Linux porteus 4.14.4-porteus #2 SMP PREEMPT Sat Dec 9 20:21:07 Local time zone must be set--s x86_64
File browser without root access. Probably, you want us to use only "mc" for root access and copying files..

First time a Porteus offer without a "wifi" interface. Quickly found out that /lib/firmware/ath10k/qca9337/hw1.0 folder was empty. Copied three bin files from my stock and Opera 45.0 module and I am here to report.

Package without a Browser. Browser selection and update tool failed for "Opera".

Applications open very slow. 5-10 seconds.

Slim authority error message during boot and lots of error messages during shutdown/reboot are present in cinnamon offer too. (LXDE was free from this)

Precision Mouse not detected. I have Kernel config files for Debian and neko's Aporteus. Noted down disabled selections in Aporteus. Where can I find Porteus Kernel config file for comparision.

I have read about a two wire communication channel in 'sm bus' for using I2C bus for HID in Microsoft website. May be a few there are disabled, in porteus kernel too.

Post Reply