Tiny Core Linux
Tiny Core Base => TCB Q&A Forum => Topic started by: windundgeist on May 19, 2021, 07:53:38 PM
-
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:
$ 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
-
@Rich
After a while I did it. Here is the first file and in the next post is the second.
-
@Rich
The second file, unfortently in two parts, as ist was to big. So here message01
-
@Rich
The second part, message02
-
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.
-
@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.
-
@administrator
Looks as I could not use the code function, or I got a server error.
test
But it is working again :)
-
@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 :)
[ 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.
-
@ 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.
-
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:
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:
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
-
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..
-
Hi windundgeist
I'd like to call your attention to this small snippet:
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.
-
@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.
-
@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.
-
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:
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.
-
@Rich
Ok, I will do it in this way. But before I will do the same thing with syslog on antiX, like you told me to do in TC. Just to see, what is going on there. Maybe you saw in my post about jOS that I have strange wlanO up while surfing? Maybe a tracker?
And just to let you know, when I was register here I first tried it with my default name JSM, but I didn't get the confirmation email for long time. Si I tried it with windundgeist and his email adress, where it was working fine. Now I have two :(. And actualy I would like JSM. Maybe you can move all the post from windundgeist to JSM, then I will delet windundgeist?
-
@Rich
I can choose whatever I like in the boot menu, the boot hangs. Here alle the lines that I see (with quiet), until the hang:
Loading /boot/vmlinuz
Loading /boot/core.gz..done
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
In the BIOS I found a possibility to enable or disable legacy for USB. If enabled I can boot the USB stick, if disabled not. So it has to do with "Wrong EFI loader signature"? In google I find a lot about, but most say to ignore it, others say, it is a problem of the USB stick. And anyway, it is booting...after the waiting time. But maybe is the stick. I don't have another.
But then the waiting time on boot also exist on the HD-installation. So the reason must be another, as there is no USB stick used.
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..
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 ")
Is it doing this, BECAUSE the USB stick has a problem? And how can we stop TC to do this? And why we have this also WITHOUT USB stick, by boot from HD-installation?
Ok, are there other ISO that I could test?
-
@Rich
Ok, after all this test I have tested it again with my old notebook, that works then and when. And...NO PROBLEM :)
So it is not the USB stick. Also on the old notebook I can see this:
Loading /boot/vmlinuz
Loading /boot/core.gz..done
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
So it is also not the EFI loader. In the BIOS I found SATA controller. I can set it on AHCI or COMPATIBLE, there is no change. Password are not any set. More BIOS settings that could be usefull I can not find.
Must have to do with my hardware? Maybe I need a other ISO?
-
@Rich
First information about my CPU:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 36 bits physical, 48 bits virtual
CPU(s): 1
On-line CPU(s) list: 0
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 15
Model name: Genuine Intel(R) CPU 585 @ 2.16GHz
Stepping: 13
CPU MHz: 2161.302
BogoMIPS: 4322.60
L1d cache: 32K
L1i cache: 32K
L2 cache: 1024K
NUMA node0 CPU(s): 0
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl tm2 ssse3 cx16 xtpr pdcm lahf_lm kaiser dtherm
Then some lines from dmesg:
[ 0.000000] Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel!
[ 3.953367] apm: BIOS not found.
[ 3.989212] Non-volatile memory driver v1.3
[ 5.235002] intel_powerclamp: No package C-state available
[ 5.235111] softdog: initialized. soft_noboot=0 soft_margin=60 sec soft_panic=0 (nowayout=0)
[ 5.235192] softdog: soft_reboot_cmd=<not set> soft_active_on_boot=0
[ 5.235274] intel_pstate: CPU model not supported
[ 5.235359] ledtrig-cpu: registered to indicate activity on CPUs
[ 5.235759] ccp_crypto: Cannot load: there are no available CCPs
[ 0.081502] L1TF: Kernel not compiled for PAE. No mitigation for L1TF
[ 0.081568] MDS: Vulnerable: Clear CPU buffers attempted, no microcode
[ 0.194034] smpboot: CPU0: Genuine Intel(R) CPU 585 @ 2.16GHz (family: 0x6, model: 0xf, stepping: 0xd)
I was reading, that PAE is not enebled in the TC kernel. Could this be the problem?
-
Hi windundgeist
I can choose whatever I like in the boot menu, the boot hangs. Here alle the lines that I see (with quiet), until the hang: ...
Select item #8, then hit tab. Edit the line that contains quiet. Change quiet to debug waitusb=5
Hitting enter should continue the boot process. That should make all the messages visible so you can see where it hangs.
... I was reading, that PAE is not enebled in the TC kernel. Could this be the problem?
No.
-
@Rich
It still hangs in the same place:
http://forum.tinycorelinux.net/index.php/topic,25011.msg159465.html#msg159465
The command line looked like this:
/boot/vmlinuz
loglevel=3
cde
showapps
lst=xbase.lst
desktop=flwm_topside
initr d=/boot/core.gz
With the last one, I'm not quite sure whether I can see everything or whether a part is "outside" the width of the screen. quiet was not there. I appended debug waitusb=5 there. The result was like in the link above.
Also thought it is not PAE. Why does it hang, but ultimately does it boot correctly? I think TC detects something that irritates it, then it waits and starts a new attempt with different conditions. Actually this should be recognizable in the code of TC. See the lines in the link above, please.
-
If there's really a space in that last line, that would likely cause a problem. "initrd" is all one word.
-
@Leee
This is interesting. I will take a look again, maybe it is just because there it switch to a new line.
EDIT: Yes, it is just the new line, so the command is correct.
@Rich
Can you take a look to dmesg from line
[ 4.369346] ata5: PATA max PIO4 cmd 0x1f0 ctl 0x3f6 irq 14
on, please. As there it hangs, but then the boot anyway is working, maybe in the next lines is the solution? Unfortently I don't understand to much about this kind of commands.
-
@Rich
I have done the installation of TC again in my old notebook, where the boot don't hangs. Then I made a dmesg.txt on the old notebook. Then I was looking for differency. In the attachment you find a file about. Maybe it helps.
And just to make it clear...after the hanging the boot works normal and I can install TC normal, without any error. Then TC works normal from frugal installation. Just also hangs on boot, like the USB-version. If I plug in a USB stick with my user-datas on running TC frugal, TC is handeling it normal, no waiting time.
-
Hi windundgeist
I'd like you to disconnect any devices not required for booting the Coreplus USB stick I had you create.
If there's a docking station, disconnect it.
If there's a USB hub, disconnect it.
External keyboards or monitors, disconnect them.
External drives, disconnect them.
Boot just the laptop and the Coreplus USB stick I had you create.
Select item #8, then hit tab. Edit the line that contains quiet. Change quiet to waitusb=5 printk.time=1 syslog.
When the system comes up, copy any messages files present in /var/log as described here:
http://forum.tinycorelinux.net/index.php/topic,24978.msg159361.html#msg159361
I don't need the dmesg.
You won't be able to write to the USB stick you booted from, so plug in and mount another USB stick or mount the internal
drive to save the files.
-
@Rich
There was never any other device connectet. It is just the notebook an the USB...an me in front of it :)
Yesterday I installed TC again on my new hardware, as frugal. Looks all fine. Of course still the waiting time on boot. It is just waiting, there are no logs on the screen during this time. Maybe TC just needs a rest there ;)
No, that was not true! There is a problem. The swap tool seams not to do anything. I understand now, that the swap you see with "free" is a zram. I can see it with cat /proc/swaps. Then I tried to create a swapfile with the terminal, using normal methodes. First of all, if I try to do a swapfiel with dd, that is bigger then 512MB, the TC blocks compleatly after the dd command. With 512MB ist works. Then chmod and mkswap work. But swapon /swapfile says that /swapfile is not a valid expression. I don't know, if there is a problem with the installation and the memory handle, because of the hang problem on boot. Or if this is just another problem, that I don't understand right. Just let you know.
So, I will do again the thing with the syslog, then post it here. Shall I do other test wit boot codes? Maybe the one that you don't like so much, to force the PAE? Or any others that I could test?
See you...and take it easy...I have the antiX running on sda1 and so there is no rush :)
-
@Rich
Ok, I have done it, boot from USB with option 8 and the 2 boot codes ad on the end of the line. In /var/log/ I could find 3 files, but just messages had something inside.
-
Hi windundgeist
... with option 8 and the 2 boot codes ...
Actually, there were 3 boot codes. You left out the waitusb=5.
I'm guessing the GUI did not come up, right?
Let's try the same thing again, but replace quiet with acpi=off waitusb=5 printk.time=1 syslog
and post the messages again.
-
@Rich
There was everything ok with the boot. I had a TC working fine. GUI was there.
So will try it again with the new boot codes soon.
-
@Rich
We have a success! TC is booting normal with acpi=off
Is this the solution already? What is TC doing without ACPI? And why it was hanging? Would be nice, if you could explain it to me.
I had to think about this video the whole time and about the "hang on, hang on, hang on" :)
https://www.youtube.com/watch?v=vxOOxLGqVHk
-
Hi windundgeist
It could be an issue with your BIOS, or one of the many configuration tables (DSDT, ACPI AML tables, etc.) that computers
have nowadays. Using acpi=off is a brute force technique that disables the entire ACPI system. If you want to try to
narrow it down further, you can try replacing acpi=off with the following boot codes one at a time to see if one
them makes things better too:
pci=noacpi, acpi=noirq, pnpacpi=off, noapic, nolapic
-
@Rich
The only boot code that has the same effect is nolapic. I have already googled it and found this:
https://askubuntu.com/questions/22311/what-is-the-impact-of-the-nolapic-parameter-on-a-multiprocessor-laptop
Don't sounds that bad, no? And as I have anyway just 1 CPU (single core), it doesn't matter, no? I will google a bit more to see, if there is any risk for the hardware, as I found that acpi=off you should not use on a notebook.
I am writing now already from my TC frugal installation. Everything seems to work fine.
Thank you so much, Rich!
Now I will enjoy my TC, because I really like it. I have Vivaldi, Fluff file manager (that is very cool!) and the normal editor. Actually I don't need a lot more to do my daily work. Maybe a small thing to write a text with some format, I don't need to much. Swapfile is not yet working, but I think I am near! And if I have to do more, I can always use the antiX (done by "anticapitalista" , well...), that has a lot of tools included.
Then I will try to get OSS running on Devuan. I could already move out all alsa stuff. Now I need to do a denylist or a blocklist, to block the alsa stuff that is in kernel. I think that OSS is working better then alsa, as I saw that alsa is not even handling the loudness reduction correct.
And then it will be time to test Fedora coreOS and see what this is able to do? Looks as it is a kind of "terminal-simulation" that let you work with Red Hat on a server. Maybe something like "jOS"?
As I am in Buenos Aires, waiting until the government is getting removed and the pandemic will go over, I have a lot of time. And maybe in this way I will be able to help some people here to go on working with there old hardware, because the economical situation is very bad. No money, no new computer.
have a very nice evening, Rich :)
-
Hi windundgeist
Since you only have 1 CPU I think it should be fine.
If you want to try something else, see if this boot code works too:
acpi_osi= That is a blank space after the equal sign. This will disable all of the "OS interface strings".
-
@Rich
No, it has no effect.
-
Hi windundgeist
Well, I'm out of ideas. So nolapic it is.
If you want to experiment with other boot codes, there are about a thousand here:
https://www.mjmwired.net/kernel/Documentation/kernel-parameters.txt
-
@Rich
Thank you, I am fine with this solution :) . If I have time, I will take a look at other boot codes. But my system seems to work fine, fast and correct.