boot process stops

[windundgeist]

When booting, the process stops after this output (both when booting from USB and from HDD frugal):

Wrong EFI loader signature
early console in extract kernel
input data 0x0071d0ae
input len ​​0x0049a1d1
output 0x00100000
output len ​​0x009be788
kernel total 0x00ad400
needet size 0x00ad400
Decompressing linux ... parsing elf ... no relocation needed ... done
Booting the kernel

If I press the power button once or twice, the boot process continues. Without I wait about 2 minutes, then it continues.

After the colored lines says:

"no dedictatet PHY driver found...maybe realtek.ko should be placed in initrams"

As I found out with google, this is apparently a problem with the kernel. Maybe in connection with my hardware? I didn't have the problem on my old notebook a few days ago. Unfortunately it is broken in the meantime :-(

However, the installation seems to be correct, I can install and work with extensions. So far I haven't encountered any problems.

What do I have to do to repair the boot and avoid the waiting time?

Here the inxi -Fxzr made with antiX:

Code: [Select]

$ inxi -Fxzr
System:
  Host: antix1 Kernel: 4.9.235-antix.1-amd64-smp x86_64 bits: 64
  compiler: gcc v: 8.3.0 Desktop: IceWM 1.8.3
  Distro: antiX-19.3_x64-full Manolis Glezos 15 October 2020
  base: Debian GNU/Linux 10 (buster)
Machine:
  Type: Laptop System: TOSHIBA product: Satellite L305 v: PSLB8U-0SVAR1
  serial: <filter>
  Mobo: TOSHIBA model: Portable PC serial: <filter> BIOS: INSYDE v: 1.80
  date: 03/20/2009
Battery:
  ID-1: BAT0 charge: 18.8 Wh condition: 19.2/22.2 Wh (86%)
  model: PA3533U-1BRS status: Charging
CPU:
  Topology: Single Core model: Intel 585 bits: 64 type: MCP arch: Core Merom
  rev: D L2 cache: 1024 KiB
  flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 4322
  Speed: 2161 MHz min/max: N/A Core speed (MHz): 1: 2161
Graphics:
  Device-1: Intel Mobile 4 Series Integrated Graphics
  vendor: Toshiba America Info Systems driver: i915 v: kernel
  bus ID: 00:02.0
  Display: x11 server: X.Org 1.20.4 driver: intel resolution: 1280x800~60Hz
  OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express v: 2.1 Mesa 18.3.6
  direct render: Yes
Audio:
  Device-1: Intel 82801I HD Audio vendor: Toshiba America Info Systems
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0
  Sound Server: ALSA v: k4.9.235-antix.1-amd64-smp
Network:
  Device-1: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet
  vendor: Toshiba America Info Systems RTL810xE driver: r8169 v: 2.3LK-NAPI
  port: 2000 bus ID: 02:00.0
  IF: eth0 state: down mac: <filter>
  Device-2: Realtek RTL8187B Wireless Adapter type: USB driver: rtl8187
  bus ID: 2-6:2
  IF: wlan0 state: up mac: <filter>
Drives:
  Local Storage: total: 149.05 GiB used: 8.83 GiB (5.9%)
  ID-1: /dev/sda vendor: Western Digital model: WD1600BEVS-26VAT0
  size: 149.05 GiB
Partition:
  ID-1: / size: 77.25 GiB used: 8.83 GiB (11.4%) fs: ext4 dev: /dev/sda1
Sensors:
  System Temperatures: cpu: 52.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/antix.list
  1: deb http://la.mxrepo.com/antix/buster buster main nonfree nosystemd
  Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
  1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ buster main
  Active apt repos in: /etc/apt/sources.list.d/buster-backports.list
  1: deb http://deb.debian.org/debian buster-backports main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
  1: deb http://ftp.us.debian.org/debian/ buster-updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list
  1: deb http://ftp.us.debian.org/debian/ buster main contrib non-free
  2: deb http://security.debian.org/ buster/updates main contrib non-free
  No active apt repos in: /etc/apt/sources.list.d/onion.list
  Active apt repos in: /etc/apt/sources.list.d/opera-stable.list
  1: deb https://deb.opera.com/opera-stable/ stable non-free
  No active apt repos in: /etc/apt/sources.list.d/various.list
  Active apt repos in: /etc/apt/sources.list.d/vivaldi.list
  1: deb http://repo.vivaldi.com/stable/deb/ stable main
Info:
  Processes: 162 Uptime: 6m Memory: 927.4 MiB used: 506.3 MiB (54.6%)
  Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3
  inxi: 3.0.36

[windundgeist]

@Rich

After a while I did it. Here is the first file and in the next post is the second.

[windundgeist]

@Rich

The second file, unfortently in two parts, as ist was to big. So here message01

[windundgeist]

@Rich

The second part, message02

[Rich]

Hi windundgeist
Click on the  Apps  icon at the bottom of the screen.
When it comes up, click  Apps->Maintenance->OnBoot maintenance.
In the  On Boot Items  panel on the right, highlight the  nautilus  entry  and click the  Delete Item from list  button.
This does not delete the extension. I just prevents it from auto loading.
Restart the system and see if the delay is still present.

[windundgeist]

@Rich

Ok I'll try it. But the chances are bad, because I have the problem from the beginning, when I booted CorePluse from the USB in order to then do the Frugal installation. I rather suspect that it is a problem with the hardware detection or a wrong driver? I didn't have the problem on my old notebook (packard bell, around 10 years old). Could it have something to do with the BIOS and the boot mode? Here is my boot sequence in the MBR, created with the tool "Grub-Customizer", installed on my antiX partition, as file. I can not post so good in the moment, it comes a Server Error.

[windundgeist]

@administrator

Looks as I could not use the code function, or I got a server error.

Code: [Select]

test

But it is working again 

[windundgeist]

@Rich

It was not nautilus. I still think it is about boot mode or hardware dedection. In my BIOS (that is 11 years old) I can not find anything about boot mode. But the boot hangs after this lines (dmesg.txt). This are the lines I can see on my screen, when the boot is waiting. At least there are some interesting things, I think...Non-volatile memory driver v1.3...Hangcheck...scsi host4: pata_legacy. I just don't understand it

Code: [Select]

[    3.975367] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
[    3.975487] ACPI: Power Button [PWRF]
[    3.982721] thermal LNXTHERM:00: registered as thermal_zone0
[    3.982789] ACPI: Thermal Zone [THRM] (48 C)
[    3.982934] isapnp: Scanning for PnP cards...
[    3.988645] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    3.989212] Non-volatile memory driver v1.3
[    3.989295] Hangcheck: starting hangcheck timer 0.9.1 (tick is 180 seconds, margin is 60 seconds).
[    4.034501] brd: module loaded
[    4.034597] mtip32xx Version 1.3.1
[    4.034796] zram: Added device: zram0
[    4.034938] VMware PVSCSI driver - version 1.0.7.0-k
[    4.035393] ata_piix 0000:00:1f.2: version 2.13
[    4.035653] ata_piix 0000:00:1f.2: MAP [ P0 -- P1 -- ]
[    4.212365] scsi host0: ata_piix
[    4.212556] scsi host1: ata_piix
[    4.212666] ata1: SATA max UDMA/133 cmd 0x4138 ctl 0x4154 bmdma 0x4110 irq 19
[    4.212736] ata2: SATA max UDMA/133 cmd 0x4130 ctl 0x4150 bmdma 0x4118 irq 19
[    4.213039] ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ]
[    4.344915] isapnp: No Plug & Play device found
[    4.349532] random: fast init done
[    4.367778] scsi host2: ata_piix
[    4.367956] scsi host3: ata_piix
[    4.368068] ata3: SATA max UDMA/133 cmd 0x4128 ctl 0x414c bmdma 0x40f0 irq 19
[    4.368138] ata4: SATA max UDMA/133 cmd 0x4120 ctl 0x4148 bmdma 0x40f8 irq 19
[    4.369230] scsi host4: pata_legacy
[    4.369346] ata5: PATA max PIO4 cmd 0x1f0 ctl 0x3f6 irq 14

The installation seems to work fine. I can handel all I need, install extensions, remove them, wifi conection, edit files. No problems. So it is just on boot. And I had it already, when I booted the CorePlus from USB to install the TC on the harddisk.

[windundgeist]

@ Rich

I wonder why the boot waits 2-3 minutes and then succeeds. Ok, if something is not recognized correctly, the boot would not work. But it works. Is the boot started again after the waiting time, but with different conditions? Or is Hangcheck the real problem in this case?

https://titanwolf.org/Network/Articles/Article?AID=784ffbbb-b576-4a5c-a04b-5295e679d323#gsc.tab=0

These users see a black screen when booting. Have these users already waited 2-3 minutes? That's a long time if you only see black

http://forum.tinycorelinux.net/index.php/topic,25015.0.html

And TC should actually boot with UEFI, with no problems. Or is my notebook not bottling with UEFI? But he uses the UEFI numbers.

http://forum.tinycorelinux.net/index.php/topic,24835.0.html

Has TC been improved to boot better, but not removed some old code that was supposed to catch boot errors?

I just think out loud, no more and no less.

[Rich]

Hi windundgeist

... But the boot hangs after this lines (dmesg.txt). This are the lines I can see on my screen, when the boot is waiting. ...

If you look at your  message01.txt  attachment in reply #2 you'll see by the timestamps that the kernel keeps running:

Code: [Select]

May 23 01:43:48 box user.info kernel: [    4.369346] ata5: PATA max PIO4 cmd 0x1f0 ctl 0x3f6 irq 14
May 23 01:43:48 box user.info kernel: [    4.581030] ata2: SATA link down (SStatus 0 SControl 300)
May 23 01:43:48 box user.warn kernel: [    4.596890] clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc-early' as unstable because the skew is too large:
May 23 01:43:48 box user.warn kernel: [    4.596978] clocksource:                       'hpet' wd_now: 209cde54 wd_last: 37ef088 mask: ffffffff
May 23 01:43:48 box user.warn kernel: [    4.597061] clocksource:                       'tsc-early' cs_now: 97361b3ff cs_last: 9321cf8da mask: ffffffffffffffff
May 23 01:43:48 box user.info kernel: [    4.597145] tsc: Marking TSC unstable due to clocksource watchdog
May 23 01:43:48 box user.info kernel: [    4.597253] clocksource: Switched to clocksource hpet
 ----- Snip -----

... Hangcheck ...

This is the description of the  hangcheck timer:

The hangcheck-timer module detects when the system has gone out to lunch past a certain margin. It can reboot the system or merely print a warning.

I see neither of those events occurring.

If you look at the end of  message02.txt  attachment in reply #3  you can see some large gaps in the timestamps:

Code: [Select]

May 23 01:44:28 box user.debug kernel: [   46.702814] wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by 28:9e:fc:04:0a:8e
May 23 01:44:40 box user.warn kernel: [   58.920271] process 'usr/local/bin/nautilus' started with executable stack
May 23 01:44:41 box daemon.info dbus-daemon[7093]: [session uid=1001 pid=7091] Activating service name='org.freedesktop.Tracker1' requested by ':1.0' (uid=1001 pid=7084 comm="nautilus --new-window ")
May 23 01:44:41 box daemon.info dbus-daemon[7093]: [session uid=1001 pid=7091] Successfully activated service 'org.freedesktop.Tracker1'
May 23 01:44:41 box daemon.info dbus-daemon[7093]: [session uid=1001 pid=7091] Activating service name='org.freedesktop.Tracker1' requested by ':1.2' (uid=1001 pid=7084 comm="nautilus --new-window ")
May 23 01:44:41 box daemon.info dbus-daemon[7093]: [session uid=1001 pid=7091] Successfully activated service 'org.freedesktop.Tracker1'
May 23 01:44:41 box daemon.info dbus-daemon[7093]: [session uid=1001 pid=7091] Activating service name='org.a11y.Bus' requested by ':1.5' (uid=1001 pid=7084 comm="nautilus --new-window ")
May 23 01:44:41 box daemon.info dbus-daemon[7093]: [session uid=1001 pid=7091] Successfully activated service 'org.a11y.Bus'
May 23 01:44:41 box daemon.info dbus-daemon[7093]: [session uid=1001 pid=7091] Activating service name='ca.desrt.dconf' requested by ':1.4' (uid=1001 pid=7084 comm="nautilus --new-window ")
May 23 01:44:41 box daemon.info dbus-daemon[7093]: [session uid=1001 pid=7091] Successfully activated service 'ca.desrt.dconf'
May 23 01:44:52 box user.warn kernel: [   70.260094] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
May 23 01:46:19 box user.err chrome[7147]: [7147:7147:0523/014619.250465:ERROR:browser_dm_token_storage_linux.cc(101)] Error: /etc/machine-id contains 0 characters (32 were expected).
May 23 01:47:51 box daemon.info dbus-daemon[7093]: [session uid=1001 pid=7091] Activating service name='org.freedesktop.Tracker1' requested by ':1.9' (uid=1001 pid=7329 comm="nautilus --new-window ")
May 23 01:47:51 box daemon.info dbus-daemon[7093]: [session uid=1001 pid=7091] Successfully activated service 'org.freedesktop.Tracker1'
May 23 01:47:51 box daemon.info dbus-daemon[7093]: [session uid=1001 pid=7091] Activating service name='org.freedesktop.Tracker1' requested by ':1.11' (uid=1001 pid=7329 comm="nautilus --new-window ")
May 23 01:47:51 box daemon.info dbus-daemon[7093]: [session uid=1001 pid=7091] Successfully activated service 'org.freedesktop.Tracker1'
May 23 01:48:08 box authpriv.notice sudo:       tc : TTY=pts/0 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/su
May 23 01:48:08 box auth.notice su: + pts/0 tc:root

[Juanito]

Something is starting the dbus daemon on boot and also trying to run nautilus and a bunch of other stuff - it looks similar to the gnome-session startup of anything in /usr/local/etc/xdg/autostart..

[Rich]

Hi windundgeist
I'd like to call your attention to this small snippet:

Code: [Select]

May 23 01:44:41 box daemon.info dbus-daemon[7093]: [session uid=1001 pid=7091] Successfully activated service 'ca.desrt.dconf'
May 23 01:44:52 box user.warn kernel: [   70.260094] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
May 23 01:46:19 box user.err chrome[7147]: [7147:7147:0523/014619.250465:ERROR:browser_dm_token_storage_linux.cc(101)] Error: /etc/machine-id contains 0 characters (32 were expected).
May 23 01:47:51 box daemon.info dbus-daemon[7093]: [session uid=1001 pid=7091] Activating service name='org.freedesktop.Tracker1' requested by ':1.9' (uid=1001 pid=7329 comm="nautilus --new-window ")Those 4 items take about 3 minutes to complete.

sbd1, your Kingston Silicon-Power 8G USB dirve might have data coruption issues.
Do you need it to Boot? Can you unplug it?

Then there's that chrome error. I don't see a chrome extension being loaded in either of the message files you posted.
Where is that coming from? Are you loading chrome from another source? If so, try disabling it.

[windundgeist]

@Rich

I don't understand a lot of all this

No, I am not using any USB to boot. I just boot from sda4.
No, I am not using Chrome in anyway.

When I was trying to import bookmarks as html in Vivaldi, the Vivaldi blocked and I could not do anything else, then press the power botton. This was a few days ago.

But I had the problem with the hanging boot from beginning on, so when I was booting the corePlus from USB to do the installation.

Still don't know, what the first line means:

Wrong EFI loader signature
early console in extract kernel
input data 0x0071d0ae
input len ​​0x0049a1d1
output 0x00100000
output len ​​0x009be788
kernel total 0x00ad400
needet size 0x00ad400
Decompressing linux ... parsing elf ... no relocation needed ... done
Booting the kernel

This was the first what I saw, when I bootet the USB with corePlus, right after the menu where I can choose the boot. I had choose the first option from the list. Since then I have this issue. But I will now just delet the installation and do it again. First I will download the corePlus ISO again and write it to a USB. On my old Notebook I have done this with a tool in Q4OS that is named "mulitwriter". In the installation here on my new Notebook I have done ist with the tool from antiX. There I have the option to write it on USB "read only" or make the USB also writebl. What shall I take? Or shall I better do it with the terminal? If so, please let me know the codes I need to type.

[windundgeist]

@Rich

Another question:

How should I handle the grub when installing TC? I have a multiboot installation and do not want TC to overwrite it. Should I NOT install the grub? These options are available in the TC installer.

[Rich]

Hi windundgeist
Download the Coreplus ISO file and make yourself a bootable USB stick.
Click on the  MountTool  icon at the bottom of the screen. Make a note of the buttons listed.
Plug in the USB stick and identify which new button(s) appear (sdb, sdc, sde, etc.).
That is the device your USB stick was assigned to.

The following will overwrite the entire contents of your USB stick.
If your USB stick is  sde  and if you downloaded  CorePlus-12.0.iso  then write the ISO to the stick like this:

Code: [Select]

dd if=CorePlus-12.0.iso of=/dev/sde
Boot the USB stick. When the menu comes up, select item #8. It should say   Boot Core with only X/GUI (TinyCore).
See if that boots any quicker.