Text Mode Boot

Non release banter
Post Reply
Bogomips
Full of knowledge
Full of knowledge
Posts: 2540
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Text Mode Boot

Post#1 by Bogomips » 06 Jan 2015, 16:14

Booting with: noload=kde cliexec=3, starts Init 4.
Booting with: noload=kde cliexec=telinit-3, starts Init 4.

Code: Select all

guest@porteus:~$ dmesg|grep command
[    0.000000] Kernel command line: quiet copy2ram ramsize=30% noauto timezone=Europe/London volume=60% noload=kde;xorg
starts Init 3.

After activating xorg and lxqt

Code: Select all

loop0     7:0    0    16M  0 loop /mnt/live/memory/images/000-kernel.xzm
loop1     7:1    0    46M  0 loop /mnt/live/memory/images/001-core.xzm
loop2     7:2    0     4K  0 loop /mnt/live/memory/images/0099-settings.xzm
loop3     7:3    0  29.2M  0 loop /mnt/live/memory/images/nVidia-304.123-porteus
loop4     7:4    0   528K  0 loop /mnt/live/memory/images/sudo-1.8.9p5-i486-1.xz
loop5     7:5    0  43.7M  1 loop /mnt/live/memory/images/002-xorg.xzm
loop6     7:6    0  35.4M  1 loop /mnt/live/memory/images/003-lxqt.xzm
Believe booting with: noload=xorg;kde optional=003-lxqt will not work i.e. desktop activated before xorg. Last time ran into problems when mate was activated before xorg in Runlevel 3.
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

User avatar
francois
Contributor
Contributor
Posts: 4942
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Text Mode Boot

Post#2 by francois » 08 Jan 2015, 21:41

What is the question here? :)
Voltaire: Le mieux est l'ennemi du bien.

User avatar
fanthom
Site Admin
Site Admin
Posts: 4566
Joined: 28 Dec 2010, 02:42
Distribution: Porteus Kiosk
Location: Poland, currently - Cork, IE
Contact:

Re: Text Mode Boot

Post#3 by fanthom » 08 Jan 2015, 21:54

'cliexec=3' is invalid, use plain '3'.
why dont you have a look on porteus.cfg how it is done there?
Please add [Solved] to your thread title if the solution was found.

Bogomips
Full of knowledge
Full of knowledge
Posts: 2540
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: Text Mode Boot

Post#4 by Bogomips » 09 Jan 2015, 00:31

@francois

No question. Just general chat. :wink:
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

Bogomips
Full of knowledge
Full of knowledge
Posts: 2540
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: Text Mode Boot

Post#5 by Bogomips » 09 Jan 2015, 17:51

Success

Code: Select all

guest@porteus:~$ dmesg|grep command
[    0.000000] Kernel command line: quiet copy2ram ramsize=30% noauto timezone=Europe/London volume=60% noload=kde norootcopy 3
In runlevel 3 lsblk (no delay)

Code: Select all

guest@porteus:~$ cat /tmp/init3 
NAME    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda       8:0    0 232.9G  0 disk 
├─sda1    8:1    0  59.6G  0 part 
├─sda2    8:2    0     1K  0 part 
├─sda3    8:3    0  70.6M  0 part 
├─sda4    8:4    0   3.8G  0 part 
├─sda5    8:5    0     4G  0 part 
├─sda6    8:6    0   1.9G  0 part 
├─sda7    8:7    0 517.7M  0 part [SWAP]
├─sda8    8:8    0   1.5G  0 part 
├─sda9    8:9    0  78.1G  0 part 
├─sda10   8:10   0  81.2G  0 part 
└─sda11   8:11   0   127M  0 part [SWAP]
sr0      11:0    1  1024M  0 rom  
loop0     7:0    0    16M  0 loop /mnt/live/memory/images/000-kernel.xzm
loop1     7:1    0    46M  0 loop /mnt/live/memory/images/001-core.xzm
loop2     7:2    0  43.7M  0 loop /mnt/live/memory/images/002-xorg.xzm
loop3     7:3    0     4K  0 loop /mnt/live/memory/images/0099-settings.xzm
loop4     7:4    0  29.2M  0 loop /mnt/live/memory/images/nVidia-304.123-porteus
loop5     7:5    0   528K  0 loop /mnt/live/memory/images/sudo-1.8.9p5-i486-1.xz

Instantaneous response for lsblk.
In runlevel 4 lsblk (delay)

Code: Select all

guest@porteus:~$ lsblk
NAME    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
fd0       2:0    1     4K  0 disk 
sda       8:0    0 232.9G  0 disk 
├─sda1    8:1    0  59.6G  0 part 
├─sda2    8:2    0     1K  0 part 
├─sda3    8:3    0  70.6M  0 part 
├─sda4    8:4    0   3.8G  0 part 
├─sda5    8:5    0     4G  0 part 
├─sda6    8:6    0   1.9G  0 part 
├─sda7    8:7    0 517.7M  0 part [SWAP]
├─sda8    8:8    0   1.5G  0 part 
├─sda9    8:9    0  78.1G  0 part 
├─sda10   8:10   0  81.2G  0 part /home/guest/p10
└─sda11   8:11   0   127M  0 part [SWAP]
sr0      11:0    1  1024M  0 rom  
loop0     7:0    0    16M  0 loop /mnt/live/memory/images/000-kernel.xzm
loop1     7:1    0    46M  0 loop /mnt/live/memory/images/001-core.xzm
loop2     7:2    0  43.7M  0 loop /mnt/live/memory/images/002-xorg.xzm
loop3     7:3    0     4K  0 loop /mnt/live/memory/images/0099-settings.xzm
loop4     7:4    0  29.2M  0 loop /mnt/live/memory/images/nVidia-304.123-porteus
loop5     7:5    0   528K  0 loop /mnt/live/memory/images/sudo-1.8.9p5-i486-1.xz
loop6     7:6    0  56.5M  1 loop /mnt/live/memory/images/003-mate.xzm

Took 13 secs. (on stop watch)
After activation of mate.xzm in runlevel 3.

It's interesting to note that this same lsblk delayed response also occurred in runlevel 3, when booting with: noload=kde load=003-mate.xzm 3. Points to the fact that activation of mate.xzm results in somehow or other delaying lsblk response.
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

Post Reply