LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


View Poll Results: Which of these installers do you prefer?
slint64-current-isolinux-menu+elilo-mini.iso 1 12.50%
slint64-current-isolinux-vesamenu+elilo-mini.iso 0 0%
slint64-current-isolinux-vesamenu-background-image+elilo-mini.iso 2 25.00%
None of them. Thay all look ugly. 5 62.50%
Voters: 8. You may not vote on this poll

Reply
  Search this Thread
Old 06-02-2016, 08:00 PM   #31
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 14.2 + Multilib
Posts: 1,483

Rep: Reputation: 918Reputation: 918Reputation: 918Reputation: 918Reputation: 918Reputation: 918Reputation: 918Reputation: 918

Didier --

I've gone thru 8 iterations of the sleep=t boot arg tests for BIOS boot.

( I accidentially did sleep=4 twice before I decided I needed a check list )

The seven dmesg files are attached.

'eleven trys' means I pressed the [1]-key 11-times at about one-second intervals before I saw the 1 echo on the screen

'one try' or '1 try' means I was able to enter the 1 without having to repeat it.

I can do the UEFI Boot if you need it but it looks like sleep=5 is the winner ...

Only allowed to load 5 files ... see post #2

-- kjh

These are the summarized results:
Code:
# grep -H -A5 '^######' sleep-[0-9].txt  # -A5 so you can see the boot command line

sleep-0.txt:############################################
sleep-0.txt-### No sleep=t boot arg took eleven tries ###
sleep-0.txt:############################################
sleep-0.txt-[    0.000000] Initializing cgroup subsys cpuset
sleep-0.txt-[    0.000000] Initializing cgroup subsys cpu
sleep-0.txt-[    0.000000] Initializing cgroup subsys cpuacct
sleep-0.txt-[    0.000000] Linux version 4.4.11 (root@hive64) (gcc version 5.3.0 (GCC) ) #2 SMP Thu May 19 02:05:49 CDT 2016
sleep-0.txt-[    0.000000] Command line: LANG=en_US.utf8 initrd=initrd BOOT_IMAGE=linux 
--
sleep-1.txt:############################################
sleep-1.txt-### took 8 tries to enter 1 ###
sleep-1.txt:############################################
sleep-1.txt-[    0.000000] Initializing cgroup subsys cpuset
sleep-1.txt-[    0.000000] Initializing cgroup subsys cpu
sleep-1.txt-[    0.000000] Initializing cgroup subsys cpuacct
sleep-1.txt-[    0.000000] Linux version 4.4.11 (root@hive64) (gcc version 5.3.0 (GCC) ) #2 SMP Thu May 19 02:05:49 CDT 2016
sleep-1.txt-[    0.000000] Command line: LANG=en_US.utf8 initrd=initrd sleep=1 BOOT_IMAGE=linux 
--
sleep-2.txt:############################################
sleep-2.txt-### took 6 trys to enter 1 ###
sleep-2.txt:############################################
sleep-2.txt-[    0.000000] Initializing cgroup subsys cpuset
sleep-2.txt-[    0.000000] Initializing cgroup subsys cpu
sleep-2.txt-[    0.000000] Initializing cgroup subsys cpuacct
sleep-2.txt-[    0.000000] Linux version 4.4.11 (root@hive64) (gcc version 5.3.0 (GCC) ) #2 SMP Thu May 19 02:05:49 CDT 2016
sleep-2.txt-[    0.000000] Command line: LANG=en_US.utf8 initrd=initrd sleep=2 BOOT_IMAGE=linux 
--
sleep-3.txt:############################################
sleep-3.txt-### took 4 trys to enter 1 ###
sleep-3.txt:############################################
sleep-3.txt-[    0.000000] Initializing cgroup subsys cpuset
sleep-3.txt-[    0.000000] Initializing cgroup subsys cpu
sleep-3.txt-[    0.000000] Initializing cgroup subsys cpuacct
sleep-3.txt-[    0.000000] Linux version 4.4.11 (root@hive64) (gcc version 5.3.0 (GCC) ) #2 SMP Thu May 19 02:05:49 CDT 2016
sleep-3.txt-[    0.000000] Command line: LANG=en_US.utf8 initrd=initrd sleep=3 BOOT_IMAGE=linux 
--
sleep-4.txt:############################################
sleep-4.txt-### took 4 tries to enter 1 ###
sleep-4.txt:############################################
sleep-4.txt-[    0.000000] Initializing cgroup subsys cpuset
sleep-4.txt-[    0.000000] Initializing cgroup subsys cpu
sleep-4.txt-[    0.000000] Initializing cgroup subsys cpuacct
sleep-4.txt-[    0.000000] Linux version 4.4.11 (root@hive64) (gcc version 5.3.0 (GCC) ) #2 SMP Thu May 19 02:05:49 CDT 2016
sleep-4.txt-[    0.000000] Command line: LANG=en_US.utf8 initrd=initrd sleep=4 BOOT_IMAGE=linux 
--
sleep-4.txt:############################################
sleep-4.txt-### took 4 trys to enter 1 ###
sleep-4.txt:############################################
sleep-4.txt-[    0.000000] Initializing cgroup subsys cpuset
sleep-4.txt-[    0.000000] Initializing cgroup subsys cpu
sleep-4.txt-[    0.000000] Initializing cgroup subsys cpuacct
sleep-4.txt-[    0.000000] Linux version 4.4.11 (root@hive64) (gcc version 5.3.0 (GCC) ) #2 SMP Thu May 19 02:05:49 CDT 2016
sleep-4.txt-[    0.000000] Command line: LANG=en_US.utf8 initrd=initrd sleep=4 BOOT_IMAGE=linux 
--
sleep-5.txt:############################################
sleep-5.txt-### took 1 try to enter 1 ###
sleep-5.txt:############################################
sleep-5.txt-[    0.000000] Initializing cgroup subsys cpuset
sleep-5.txt-[    0.000000] Initializing cgroup subsys cpu
sleep-5.txt-[    0.000000] Initializing cgroup subsys cpuacct
sleep-5.txt-[    0.000000] Linux version 4.4.11 (root@hive64) (gcc version 5.3.0 (GCC) ) #2 SMP Thu May 19 02:05:49 CDT 2016
sleep-5.txt-[    0.000000] Command line: LANG=en_US.utf8 initrd=initrd sleep=5 BOOT_IMAGE=linux 
--
sleep-6.txt:############################################
sleep-6.txt-### took one try to enter 1 ###
sleep-6.txt:############################################
sleep-6.txt-[    0.000000] Initializing cgroup subsys cpuset
sleep-6.txt-[    0.000000] Initializing cgroup subsys cpu
sleep-6.txt-[    0.000000] Initializing cgroup subsys cpuacct
sleep-6.txt-[    0.000000] Linux version 4.4.11 (root@hive64) (gcc version 5.3.0 (GCC) ) #2 SMP Thu May 19 02:05:49 CDT 2016
sleep-6.txt-[    0.000000] Command line: LANG=en_US.utf8 initrd=initrd sleep=6 BOOT_IMAGE=linux 
--
sleep-7.txt:############################################
sleep-7.txt-### took one try to enter one ###
sleep-7.txt:############################################
sleep-7.txt-[    0.000000] Initializing cgroup subsys cpuset
sleep-7.txt-[    0.000000] Initializing cgroup subsys cpu
sleep-7.txt-[    0.000000] Initializing cgroup subsys cpuacct
sleep-7.txt-[    0.000000] Linux version 4.4.11 (root@hive64) (gcc version 5.3.0 (GCC) ) #2 SMP Thu May 19 02:05:49 CDT 2016
sleep-7.txt-[    0.000000] Command line: LANG=en_US.utf8 initrd=initrd sleep=7 BOOT_IMAGE=linux
This is what I did each time after I got to the slint commandline ( so I don't forget )

Code:
set -o vi                          # vi-mode is the 2nd best thing to the gpm daemon <G>
mkdir /mnt/hdd
mount /dev/sda4 /mnt/hdd
/mnt/hdd/tmp/slint/dm N Message    # dm is a script ; N is the sleep=N integer ; Message is a note ( see below )
sync
sync
umount /mnt/hdd
This is /mnt/hdd/tmp/slint/dm:

Code:
#!/bin/sh
#
TDir="/mnt/hdd/tmp/slint"
#
[ $# -lt 1 ] && echo "usage `basename $0` int [ message ]" >&2 && exit 1
#
TNam="$TDir/sleep-$1.txt" ; shift
#
Mess="$@"

if [ "$Mess" != "" ]
then
   echo "############################################" >> $TNam
   echo -e "### $Mess ###"                             >> $TNam
   echo "############################################" >> $TNam
fi

dmesg >> $TNam
These are the dmesg files:

Code:
# ssh -p XXXX -l root id92   # this is the test box booted to CentOS 6.8
# cd /tmp/slint              # this is /mnt/sda4/tmp/slint/ in the do-list below
# ls -la 

total 484
drwxr-xr-x  3 root root   4096 Jun  2 19:16 .
drwxrwxrwt. 6 root root   4096 Jun  2 19:15 ..
-rwxr-xr-x  1 root root    387 Jun  1 13:48 dm
drwxr-xr-x  2 root root   4096 Jun  1 13:38 old
-rw-r--r--  1 root root  51972 Jun  1 13:49 sleep-0.txt
-rw-r--r--  1 root root  51974 Jun  1 13:51 sleep-1.txt
-rw-r--r--  1 root root  51973 Jun  1 13:55 sleep-2.txt
-rw-r--r--  1 root root  51973 Jun  1 13:58 sleep-3.txt
-rw-r--r--  1 root root 103947 Jun  1 14:06 sleep-4.txt  # oops ! ran this twice
-rw-r--r--  1 root root  51972 Jun  1 14:09 sleep-5.txt
-rw-r--r--  1 root root  51974 Jun  1 14:12 sleep-6.txt
-rw-r--r--  1 root root  51976 Jun  1 14:14 sleep-7.txt
Attached Files
File Type: txt sleep-0.txt (50.8 KB, 2 views)
File Type: txt sleep-1.txt (50.8 KB, 2 views)
File Type: txt sleep-2.txt (50.8 KB, 5 views)
File Type: txt sleep-3.txt (50.8 KB, 4 views)
File Type: txt sleep-4.txt (101.5 KB, 5 views)

Last edited by kjhambrick; 06-02-2016 at 08:05 PM. Reason: hide port
 
Old 06-02-2016, 08:01 PM   #32
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 14.2 + Multilib
Posts: 1,483

Rep: Reputation: 918Reputation: 918Reputation: 918Reputation: 918Reputation: 918Reputation: 918Reputation: 918Reputation: 918
dmesg sleep=N files ... Continued ...
Attached Files
File Type: txt sleep-5.txt (50.8 KB, 4 views)
File Type: txt sleep-6.txt (50.8 KB, 3 views)
File Type: txt sleep-7.txt (50.8 KB, 6 views)
 
Old 06-03-2016, 08:08 AM   #33
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 9,013

Original Poster
Rep: Reputation: Disabled
Thanks for your tests, kjhambrick.

So, in next alpha ISO I will just insert a line with "sleep 5" before the dialog as a workaround.

Something puzzles me. I see that in all your sleep-?.txt logs, your keyboard is registered @ around 12 seconds.

I can't check here as I have nothing that uses the same driver xhci_hcd.

However as you do I have an optical mouse that uses ushid. In one of your logs, I see:
Code:
bash-4.3$ grep "interface driver usbhid" *txt
sleep-0.txt:[   11.761213] usbcore: registered new interface driver usbhid
sleep-1.txt:[   11.725631] usbcore: registered new interface driver usbhid
sleep-2.txt:[   11.887150] usbcore: registered new interface driver usbhid
sleep-3.txt:[   11.764883] usbcore: registered new interface driver usbhid
sleep-4.txt:[   11.745980] usbcore: registered new interface driver usbhid
sleep-4.txt:[   11.719803] usbcore: registered new interface driver usbhid
sleep-5.txt:[   11.743498] usbcore: registered new interface driver usbhid
sleep-6.txt:[   11.726665] usbcore: registered new interface driver usbhid
sleep-7.txt:[   11.751806] usbcore: registered new interface driver usbhid
bash-4.3$
Here, also with a huge kernel huge 4.4.11 I have something similar:
Code:
[   12.230067] usbcore: registered new interface driver usbhid
Hovever, in Slackware 14.1 with a kernel huge 3.10.17-smp:
Code:
[    8.550422] usbcore: registered new interface driver usbhid
Similarly, with kernel 4.4.11
Code:
[   12.285983] input: Logitech USB Optical Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:046D:C077.0001/input/input12
But with 3.10.17:
Code:
[    8.555729] input: Logitech USB Optical Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input5
I won't draw hastily conclusions and my Slackware 14.1 is 32-bit, but still I am puzzled by this difference of 3.3 seconds with 4.4.11.
 
Old 06-03-2016, 08:52 AM   #34
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 14.2 + Multilib
Posts: 1,483

Rep: Reputation: 918Reputation: 918Reputation: 918Reputation: 918Reputation: 918Reputation: 918Reputation: 918Reputation: 918
Didier --

Yes, it seems that all that timing stuff is as you said due to entropy ...

Is `logger` available in the install environment ?

And does logger append to `dmesg` output ?

If so, I wonder if you can sprinkle a few strategically placed logger calls in rc.S ?

-- kjh
 
Old 06-03-2016, 04:08 PM   #35
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 9,013

Original Poster
Rep: Reputation: Disabled
kjhambrick --

Another test if you agree

I try to have the kernel module for your USB keyboard, xhci-hcd, loaded sooner, see this post.

Please try this ISO:
http://slint.fr/testing/slint64-curr...p-xhci-hcd.iso
Its md5 checksum is:
http://slint.fr/testing/slint64-curr...ci-hcd.iso.md5

I would like to know if your kernel is ready even without appending any sleep=n kernel parameters, or at least with a smaller value than 5.

Thanks in advance
 
Old 06-03-2016, 04:21 PM   #36
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 14.2 + Multilib
Posts: 1,483

Rep: Reputation: 918Reputation: 918Reputation: 918Reputation: 918Reputation: 918Reputation: 918Reputation: 918Reputation: 918
Didier --

I've grabbed it.

I'll burn it and test it for tomorrow morning.

Code:
# md5sum -c slint64-current-sleep-xhci-hcd.iso.md5

slint64-current-sleep-xhci-hcd.iso: OK
-- kjh
 
Old 06-03-2016, 04:36 PM   #37
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 9,013

Original Poster
Rep: Reputation: Disabled
kjhambrick --

I realize now that rc.usb runs only if udev is not used so basically the new ISO won't change anything, alas.

However you could append:
noudev
to the command line as then rc.usb will run, and see what happens.
 
Old 06-04-2016, 06:43 AM   #38
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 14.2 + Multilib
Posts: 1,483

Rep: Reputation: 918Reputation: 918Reputation: 918Reputation: 918Reputation: 918Reputation: 918Reputation: 918Reputation: 918
Quote:
Originally Posted by Didier Spaier View Post
kjhambrick --

I realize now that rc.usb runs only if udev is not used so basically the new ISO won't change anything, alas.

However you could append:
noudev
to the command line as then rc.usb will run, and see what happens.
Didier --

When I appended noudev to the kernel parameters, I was unable to type anything at all and I had to do a hard reset to reboot.

I booted the same ISO without the noudev parm:

no sleep - 8 tries
sleep=3 - 4 tries
sleep=5 - 1 try ( responded as expected )

The dmesg files are attached.

-- kjh

Code:
# grep -H -A5 '^######' noudev-sleep-[0-9].txt

noudev-sleep-0.txt:############################################
noudev-sleep-0.txt-### took eight 1-chars to respond ###
noudev-sleep-0.txt:############################################
noudev-sleep-0.txt-[    0.000000] Initializing cgroup subsys cpuset
noudev-sleep-0.txt-[    0.000000] Initializing cgroup subsys cpu
noudev-sleep-0.txt-[    0.000000] Initializing cgroup subsys cpuacct
noudev-sleep-0.txt-[    0.000000] Linux version 4.4.12 (root@hive64) (gcc version 5.3.0 (GCC) ) #2 SMP Wed Jun 1 17:04:52 CDT 2016
noudev-sleep-0.txt-[    0.000000] Command line: LANG=en_US.utf8 initrd=initrd BOOT_IMAGE=linux 
--
noudev-sleep-3.txt:############################################
noudev-sleep-3.txt-### took four 1-chars to respond ###
noudev-sleep-3.txt:############################################
noudev-sleep-3.txt-[    0.000000] Initializing cgroup subsys cpuset
noudev-sleep-3.txt-[    0.000000] Initializing cgroup subsys cpu
noudev-sleep-3.txt-[    0.000000] Initializing cgroup subsys cpuacct
noudev-sleep-3.txt-[    0.000000] Linux version 4.4.12 (root@hive64) (gcc version 5.3.0 (GCC) ) #2 SMP Wed Jun 1 17:04:52 CDT 2016
noudev-sleep-3.txt-[    0.000000] Command line: LANG=en_US.utf8 initrd=initrd sleep=3 BOOT_IMAGE=linux 
--
noudev-sleep-5.txt:############################################
noudev-sleep-5.txt-### took one 1-char to respond ###
noudev-sleep-5.txt:############################################
noudev-sleep-5.txt-[    0.000000] Initializing cgroup subsys cpuset
noudev-sleep-5.txt-[    0.000000] Initializing cgroup subsys cpu
noudev-sleep-5.txt-[    0.000000] Initializing cgroup subsys cpuacct
noudev-sleep-5.txt-[    0.000000] Linux version 4.4.12 (root@hive64) (gcc version 5.3.0 (GCC) ) #2 SMP Wed Jun 1 17:04:52 CDT 2016
noudev-sleep-5.txt-[    0.000000] Command line: LANG=en_US.utf8 initrd=initrd sleep=5 BOOT_IMAGE=linux
-- kjh
Attached Files
File Type: txt noudev-sleep-0.txt (50.7 KB, 2 views)
File Type: txt noudev-sleep-3.txt (50.8 KB, 2 views)
File Type: txt noudev-sleep-5.txt (50.8 KB, 3 views)
 
1 members found this post helpful.
Old 06-04-2016, 06:59 AM   #39
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 9,013

Original Poster
Rep: Reputation: Disabled
kjhambrick --

Thanks again for your tests and your patience. Much appreciated.

So, I will just write "sleep 5" in rc.S and make no other change.

Also, I will keep the graphical isolinux menu with the landscape, thus I mark this thread as [SOLVED].
 
Old 06-04-2016, 07:39 AM   #40
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 14.2 + Multilib
Posts: 1,483

Rep: Reputation: 918Reputation: 918Reputation: 918Reputation: 918Reputation: 918Reputation: 918Reputation: 918Reputation: 918
Didier --

One thing I've thought of since I started playing with Alien Bob's slackware64-live-current.iso on the same Zotac ZBOX ID92 Box ...

I've been making a luks-encryppted $HOME Dir on the USB.

If slackware64-live-current was having the same issue activating my flakey cheap USB Keyboard, my luks password would fail and I imagine I would have a mess on my hands.

Or at least the mount would fail.

I understand that there's a fundamental difference here -- the slint test.iso files are slimmed-down Slackware Installer Boot 'disks'.

While Eric's slackware64-live-current.iso is a full-blown slackware Current System on a bootable USB Drive and the kernel and initrd are different than the slint kernel and initrd

But maybe there's a hint in the attached dmesg file from Eric's .iso ?

Here's the current liveslak 'version'

Code:
# cat /home/dld/alien/liveslak/current/slackware64-current-live/LATEST_ADDITION_TO_CURRENT

Fri Jun 3 23:36:07 UTC 2016
I booted the liveslak current image, logged in as root and immediately typed dmesg > /root/liveslak-current-dmesg.txt

HTH.

-- kjh
Attached Files
File Type: txt liveslak-current-dmesg.txt (54.8 KB, 9 views)
 
Old 06-04-2016, 12:06 PM   #41
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 9,013

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by kjhambrick View Post
I booted the liveslak current image, logged in as root and immediately typed dmesg > /root/liveslak-current-dmesg.txt
I see that your keyboard is available around 5 seconds sooner. If only I could understand why...
 
Old 06-04-2016, 02:33 PM   #42
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 14.2 + Multilib
Posts: 1,483

Rep: Reputation: 918Reputation: 918Reputation: 918Reputation: 918Reputation: 918Reputation: 918Reputation: 918Reputation: 918
Quote:
Originally Posted by Didier Spaier View Post
I see that your keyboard is available around 5 seconds sooner. If only I could understand why...
Me too.

I am 'studying up' on the overlay file system and loop mounts on Eric's liveslack ISO.

I see the generic kernel and the initrd.img in /mnt/livemedia/boot/

According to the dmesg output I attached earlier, these are the 'running images'

But I've no idea to tell which modules are loaded and in what order without a lot of digging.

-- kjh
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
High throughput non-blocking Server Design: Alternatives to Busy Wait amitkriit Programming 0 12-01-2013 05:47 PM
High throughput non-blocking Server Design: Alternatives to Busy Wait amitkriit Linux - Server 1 11-30-2013 09:10 AM
How to release a busy resource yougant Linux - Newbie 5 07-03-2013 12:31 AM
amarok busy wait jiml8 Linux - Software 0 06-29-2007 10:17 AM
Using Ubuntu, interested in Sarge; should I wait for the release? audiorevolution Debian 5 05-20-2005 08:03 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:55 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration