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: 3423
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#1 by Ed_P » 05 Dec 2017, 05:52

I have a script that makes a module of changes I've made to 3.2.2. I determine what files have changed by letting the system quiesce, making my change then running the changes command to find what changed. I then add the names of the changed file to my module script. (ref: http://forum.porteus.org/viewtopic.php? ... 776#p27204)

When testing 4.0 I have included mychanges.xzm module in the 4.0 Modules folder. This worked up until the 1203 update. Then booting resulted in the system hanging with a black screen. If I moved my changes module to the Optional folder and booted the system booted fine. And if I then manually Activated mychanges.xzm module they were incorporated into the running system.

After many tweaks to mychanges script I found the lines causing the system to hang when booting were one or more of these:

Code: Select all

#                  -- Network files --
#cp -a --parents    /etc/NetworkManager/system-connections/*       /tmp/mod/
#cp -a --parents    /var/run/NetworkManager/*                      /tmp/mod/
#cp -a --parents    /var/lib/dhcpcd/*                              /tmp/mod/
#cp -a --parents    /etc/hosts                                     /tmp/mod/

Why?

If when the system hung I executed:

Alt+PrtScr+r
Alt+PrtScr+e
Alt+PrtScr+i

The system would start then issue msgs like these before stopping with "INIT: Id 'x1' respawning too fast":

Code: Select all

(Cinnamon-killer-daemon:1442): Gdk-Critical ***: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)'
and a similar msg stating

Code: Select all

'GDK_IS_SCREEN (screen) failed'
I do not understand the connection between network files and booting hangs with Display/Screen errors.
:%)
Ed

User avatar
Ed_P
Contributor
Contributor
Posts: 3423
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#2 by Ed_P » 05 Dec 2017, 18:53

Well, not these two, the system boots fine. It's one of the NetworkManager files.

Code: Select all

#                  -- Network files --
#cp -a --parents    /etc/NetworkManager/system-connections/*       /tmp/mod/
#cp -a --parents    /var/run/NetworkManager/*                      /tmp/mod/
cp -a --parents    /var/lib/dhcpcd/*                              /tmp/mod/
cp -a --parents    /etc/hosts                                     /tmp/mod/
Ed

roadie
Full of knowledge
Full of knowledge
Posts: 206
Joined: 02 Jan 2011, 18:41
Distribution: Porteus 3.5...with a twist
Location: In a hayfield

3.2.2 migration to 4.0 problem.

Post#3 by roadie » 05 Dec 2017, 19:45

Ed_P,
Probably completely unrelated, but I had a similar problem with installing my Porteus-Runit build to an Acer laptop. It turned out to be permissions for /home/guest. As I recall, the problem was in permissions for /home/guest/.dconf. I haven't yet tracked down what file is changing permissions. It prevented NetworkManager starting for guest, and also at first, an X session for guest.

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

3.2.2 migration to 4.0 problem.

Post#4 by brokenman » 05 Dec 2017, 22:35

Please wait until version 4.0 has been released. :hammer:
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Ed_P
Contributor
Contributor
Posts: 3423
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#5 by Ed_P » 05 Dec 2017, 22:52

Just preparing for the future. ;)

The 3.2.2 files involved:

Code: Select all

guest@porteus:~$ ls -l /etc/NetworkManager/system-connections/
total 24
-rw------- 1 root root 442 Aug 23 09:11 Auto\ FiOS-03KMH-5G
-rw------- 1 root root 428 Dec 31  2016 Auto\ OGLES-WIFI
-rw------- 1 root root 428 Feb 18  2017 Auto\ QuickMoose-f1a2ae39-358c-463c-a8e2-f08cb56192e2
-rw------- 1 root root 339 Oct  4 16:21 Auto\ RRH_guest
-rw------- 1 root root 423 Jun  3  2017 Auto\ hobbolly
-rw------- 1 root root 340 Jun  4  2017 gogoinflight
guest@porteus:~$ ls -l /var/run/NetworkManager/
total 8
-rw-r--r-- 1 root root   4 Dec  5 17:15 NetworkManager.pid
srwxr-xr-x 1 root root   0 Dec  5 17:15 private-dhcp=
-rw-r--r-- 1 root root 130 Dec  5 17:15 resolv.conf
guest@porteus:~$ 

On a slight tangent, in Terminal, the up arrow takes me back days!! How far back does Terminal command history go? And is there an option to control that? :)
Ed

User avatar
Ed_P
Contributor
Contributor
Posts: 3423
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#6 by Ed_P » 06 Dec 2017, 17:55

Don't know about the /var/run/NetworkManager/ files but the /etc/NetworkManager/system-connections/ ones definitely cause the problem. :happy62:
Ed

User avatar
wread
Module Guard
Module Guard
Posts: 1116
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v3.2.5-kde5-64 bits
Location: Santo Domingo
Contact:

3.2.2 migration to 4.0 problem.

Post#7 by wread » 08 Dec 2017, 10:54

In my system I run NetworkManager 1.10.0 since a week ago without complains, Maybe you should search the culprit somewhere else...
Testing 001-core 1203 I found it lacked the header files of readline-7, that supposedly should be in 05-devel (crazy?). Try this change (putting readline headers in 001-core) to see if that was it. By the way I do not know what has Python to do in 001-core (already over 100Mb)

Regards!
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
brokenman
Site Admin
Site Admin
Posts: 5657
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

3.2.2 migration to 4.0 problem.

Post#8 by brokenman » 08 Dec 2017, 21:31

Try this change (putting readline headers in 001-core) to see if that was it.
Why would header files make any difference wread?

Check your permissions Ed_P
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Ed_P
Contributor
Contributor
Posts: 3423
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#9 by Ed_P » 08 Dec 2017, 21:32

Thank you wread but a little beyond my capabilities. :D I'm an ISO booter.

Why would file permissions created by 4.0 1203 cause 4.0 to hang when booting. 3.2.2's network files that I backup didn't cause 4.0 1120 to hang when booting. :%)

What permissions would you like me to check brokenman?
Ed

User avatar
Ed_P
Contributor
Contributor
Posts: 3423
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#10 by Ed_P » 09 Dec 2017, 00:13

4.0 1203 Cinnamon files

Code: Select all

guest@porteus:~$ ls -l /etc/NetworkManager/system-connections/
total 4
-rw------- 1 root root 350 Dec  8 19:00 Auto\ QuickMoose
guest@porteus:~$ ls -l /var/run/NetworkManager
total 8
-rw-r--r-- 1 root root   3 Dec  8 18:59 NetworkManager.pid
drwxr-xr-x 2 root root  40 Dec  8 18:59 devices/
srwxr-xr-x 1 root root   0 Dec  8 19:00 private-dhcp=
-rw-r--r-- 1 root root 142 Dec  8 19:00 resolv.conf
4.0 1203 Cinnamon save.dat files

Code: Select all

guest@porteus:~$ mloop /mnt/sda6/porteus4.0/changes/porteussave.dat
 Please enter root's password below 
Password: 
using /dev/loop4

Please wait while i gather some info ....

 #################################
 Your data file has been mounted at: 
/mnt/loop

You can unmount it by typing uloop

Here is a list of the files:
etc  home  root  usr  var

guest@porteus:~$ ls -l /mnt/loop/etc/NetworkManager/system-connections/
total 4
-rw------- 1 root root 350 Dec  8 00:25 Auto\ QuickMoose
guest@porteus:~$ ls -l /mnt/loop/var/run/NetworkManager
/bin/ls: cannot access '/mnt/loop/var/run/NetworkManager': No such file or directory
guest@porteus:~$ ls -l /mnt/loop/var/
total 0
drwxr-xr-x 4 root root  36 Dec  8 00:17 cache/
drwxr-xr-x 7 root root  79 Dec  8 00:27 lib/
drwxrwxrwt 2 root root   6 Dec  7 19:33 lock/
drwxr-xr-x 4 root root 237 Dec  8 00:17 log/
drwxr-xr-x 3 root root  18 Dec  8 00:17 spool/
guest@porteus:~$ 
If Network Manager is a part of Cinnamon and not Porteus fixing this could be awhile. jssouza won't be back till January.
Ed

User avatar
wread
Module Guard
Module Guard
Posts: 1116
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v3.2.5-kde5-64 bits
Location: Santo Domingo
Contact:

3.2.2 migration to 4.0 problem.

Post#11 by wread » 09 Dec 2017, 12:06

Why would header files make any difference wread?
Can I delete /usr/include/ from 001-core Jay?
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: 1116
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v3.2.5-kde5-64 bits
Location: Santo Domingo
Contact:

3.2.2 migration to 4.0 problem.

Post#12 by wread » 09 Dec 2017, 12:09

@Ed_P Do you have 05-devel in base? If you don't, put it there and test again...

Good luck!
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
brokenman
Site Admin
Site Admin
Posts: 5657
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

3.2.2 migration to 4.0 problem.

Post#13 by brokenman » 09 Dec 2017, 20:59

Wread, header files are only used at compile time. At run time they're not needed.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Ed_P
Contributor
Contributor
Posts: 3423
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#14 by Ed_P » 09 Dec 2017, 23:02

Ok, a fresh start. OS porteus-4.0-x86_64-20171203.iso DE 003-cinnamon-x86_64-20171204.xzm

1. Boot ISO with no changes=EXIT cheatcode and create a new porteussave.dat file. Exit
2. Boot ISO with changes=EXIT cheatcode. System boots fine. Do not connect to network. Activate 3.2.2 changes. Exit saving changes.
3. Boot ISO with changes=EXIT cheatcode. System boots fine. Connect to wi-fi network. Exit saving changes.
4. Boot ISO with changes=EXIT cheatcode. System hangs booting.
5. Press Alt+PrtScr+E. The booting continues and displays the GDK_IS_DISPLAY and GDK_IS_SCREEN error msgs like before. Stops at respawning too fast.
6. Press Enter. Signon as root and enter startx.
7. Booting continues with error msgs.

Code: Select all

  /usr/bin/startx: line 159: hostname: command not found.
  many print_req_errors
  SQUASHFS error: Unable to read fragmented cache
  SQUASHFS error: Unable to read page block
  line 171: /usr/bin/mcookie: Input/output error
  Couldn't create cookie
8. The DE comes up. With an error window saying Cinnamon crashed.
Ed

Jack
Contributor
Contributor
Posts: 1259
Joined: 09 Aug 2013, 14:25
Distribution: Porteus 3.2.rc5 Mate 64 bit
Location: Marysville, OHIO USA

3.2.2 migration to 4.0 problem.

Post#15 by Jack » 09 Dec 2017, 23:32

When I create a new USB and the iso is dated 20171203. And I use the porteus.cfg. Here is the one I use.

Code: Select all

LABEL GRAPHICAL
MENU LABEL Graphics mode
KERNEL vmlinuz
APPEND initrd=initrd.xz changes=/porteus
TEXT HELP
    Run Porteus the best way we can.
    Try to autoconfigure graphics
    card and use the maximum
    allowed resolution
ENDTEXT
On first boot it boots up great and create the changes directory in porteus. On 2nd boot up it hangs. So I reboot into text mode and delete changes it the porteus directory. Then I reboot it boot up great. Hope this help and hope you understand it.
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.

Post Reply