Tiny Core Linux
Tiny Core Base => TCB Bugs => Topic started by: vito on August 13, 2024, 01:38:49 PM
-
Steps:
1. Select TinyCorePure64-15.0 iso in Ventoy menu
2. Choose any option: boot normal, grub or memdisk
3. Choose any option, e.g. tc.
Actual result:
Black screen, nothing happens after pressing any key.
Expected result:
Successful boot and shell command line.
Environment: laptop Dell XPS 15, 11th Gen Intel(R) Core(TM) i5-11400H, 16 GB RAM, USB, FAT32 file system, GPT, UEFI. Ventoy 1.0.99
Logs:
disk/efi/efidisk.c:581: reading 0x140 sectors at the sector 0x1480 from cdo
disk/efi/efidisk.c:581: reading Ox140 sectors at the sector 0x15co from cdo
disk/efi/efidisk.c:581: reading 0x140 sectors at the sector 0x1700 from cdo
disk/efi/efidisk.c:581: reading 0x140 sectors at the sector 0x1840 from cdo
disk/efi/efidisk.c:581: reading 0x140 sectors at the sector 0x1980 from cdo
disk/efi/efidisk.c:581: reading 0x140 sectors at the sector 0x1aco from cdo
disk/efi/efidisk.c:581: reading 0x140 sectors at the sector 0x1c00 from cdo
disk/efi/efidisk.c:581: reading 0x140 sectors at the sector 0x1d40 from cdo
disk/efi/efidisk.c:581: reading 0x140 sectors at the sector 0x1e80 from cdo
disk/efi/efidisk.c:581: reading 0x140 sectors at the sector 0x1fco from cdo
disk/efi/efidisk.c:581: reading 0x140 sectors at the sector 0x2100 from cdo
disk/efi/efidisk.c:581: reading oxc0 sectors at the sector 0x2240 from cdo
disk/efi/efidisk.c:581: reading Ox10 sectors at the sector 0x2300 from cdo
loader/i386/linux.c:1124: Initrd, addr=0x9726a000, size=0xd8551c
kern/disk.c:295: Closing `cd0'.
disk/efi/efidisk.c:553: closing cd0
script/script.c:65: free 0x52e862e0
script/script.c:65: free 0x52e86320 `
script/script.c:65: free 0x52e86360 :
script/script.c:65: free 0x52e85dco
script/script.c:65: free 0x52e85e20
script/script.c:65: free 0x52e85e60
script/script.c:65: free 0x52e85eco
script/script.c:65: free 0x52e85f20
script/script.c:65: free 0x52e85f80
script/script.c:65: free 0x52e86180
script/script.c:65: free 0x52e861e0
script/script.c:65: free 0x52e86220
script/lexer.c:322: token 259 text [
]
script/script .c:50: malloc 0x52e86240
script/script.c:50: malloc Ox52e86200
script/lexer.c:322: token 0 text []
script/script.c:50: malloc 0x52e86380
script/script.c:50: malloc 0x52e86340
script/script.c:65: free 0x52e86340
script/script.c:65: free 0x52e86380
script/script.c:65: free 0x52e86200
script/script.C:65: free 0%52e86240
script/lexer.c:322: token 259 text [
]
script/script.c:50: malloc x52e86240
script/script.c:50: malloc 0x52e86200
script/lexer.c:322: token 0 text []
script/script.c:50: malloc 0x52e86380
script/script.c:50: malloc 0x52e86340
script/script.c:65: free 0x52e86340
script/script.c:65: free 0x52e86380
script/script.c:65: free 0x52e86200
script/script.c:65: free 0x52e86240
-
Make sure any secure boot bios options are disabled, and then see the various debug and early debug kernel boot options in kernel-parameters.txt.
-
Despite secure boot disabled and various debug and early debug kernel boot options (debug earlyprintk=vga ioremap_debug, earlycon, ekgdboc, trace_vent=*.* stacktrace) the result is the same (screen is black).
-
check this out and keep us posted on your progress!
https://github.com/ventoy/Ventoy/issues/214
-
Unfortunately, disabling Intel Rapid Start (by setting "Block Sleep" on in Power section in BIOS) didn't resolve the issue. Also, disabling Intel Speed Shift Technology didn't do. GRUB bootloader logs are very similar. Any other hints, perhaps?
To avoid doubts, Ubuntu and other Linux distros boot correctly on the same laptop and USB so the issue seems to be with TinyCorePure64 only. Fortunately, it is possible to reboot laptop by pressing ctrl+alt+del for a few seconds.
-
Logs (tail) attached.
-
... and the preceding screen of logs.
-
check this out and keep us posted on your progress!
https://github.com/ventoy/Ventoy/issues/214
disable "Intel Rapid Start Technology" in BIOS > Config > Power!
-
Hi vito
Try adding some wait time. When the Tinycore boot menu
comes up, hit the tab key and add this to the boot options:
waitusb=10
-
disable "Intel Rapid Start Technology" in BIOS > Config > Power!
There isn't any "Intel Rapid Start Technology" in BIOS > Config > Power on my Dell laptop.
-
Hi vito
Try adding some wait time. When the Tinycore boot menu
comes up, hit the tab key and add this to the boot options:
waitusb=10
Unfortunately, waitusb=10 didn't resolved the issue.
-
does it work properly without ventoy?
i also had a similar problem with ventoy+porteus. lucky for me, the boot worked correctly with the grub option.
-
looks like that unit was available with more than one graphics option(intel or nvidia)
https://arstechnica.com/gadgets/2021/09/dell-xps-15-9510-review-a-gorgeous-well-balanced-workstation-laptop/
-
searched the forum for instances/mentions of ventoy and this was one of them:
https://forum.tinycorelinux.net/index.php/topic,23363.msg165688.html#msg165688
tl;dr:
post suggests trying acpi=noirq
-
There isn't any "Intel Rapid Start Technology" in BIOS > Config > Power on my Dell laptop.
wrt>Black screen TinyCorePure64-15.0 and Ventoy
perhaps something about your configuration
inspires your computer to enter (undocumented) "goth mode" :P
... it could be working fine with black gothic-font on black background!
looks like that unit was available with more than one graphics option(intel or nvidia)
https://arstechnica.com/gadgets/2021/09/dell-xps-15-9510-review-a-gorgeous-well-balanced-workstation-laptop/
https://www.dell.com/community/en/conversations/laptops-general-locked-topics/is-intel-rapid-start-useless-on-xps-15-9530-if-hdd-swapped-for-ssd/647f4761f4ccf8a8def97a95
...
https://www.dell.com/support/home/en-uk/drivers/driversdetails?driverid=crrkj#SupportedOs
does it work properly without ventoy?
i also had a similar problem with ventoy+porteus. lucky for me, the boot worked correctly with the grub option.
standalone efi @ https://www.supergrubdisk.org/category/download/supergrub2diskdownload/super-grub2-disk-stable/
might be useful to test alt ldr?...
-
tl;dr:
post suggests trying acpi=noirq
"acpi=noirq" didn't resolve the issue, unfortunately.
I haven't tried booting in another way than Ventoy yet.
-
::) ::) ::)
does it work properly without ventoy?
i also had a similar problem with ventoy+porteus. lucky for me, the boot worked correctly with the grub option.
standalone efi @ https://www.supergrubdisk.org/category/download/supergrub2diskdownload/super-grub2-disk-stable/
might be useful to test alt ldr?...
-
Hi vito
... To avoid doubts, Ubuntu and other Linux distros boot correctly on the same laptop and USB so the issue seems to be with TinyCorePure64 only. Fortunately, it is possible to reboot laptop by pressing ctrl+alt+del for a few seconds.
So other ISOs are booting correctly using Ventoy, right?
-
So other ISOs are booting correctly using Ventoy, right?
Right.
-
@vito, after some investigation it appears that Ventoy is currently failing for some users regardless of the operating system they are attempting to boot/install/live-run/etc
the version we have been experimenting with is:
(sha1 checksum 30bdd6023d81ea09ec5b19f5924ec92c56f96538 ventoy-1.0.99-linux.tar.gz)
so it isn't TinyCoreLinux failing...it is Ventoy. hopefully the Ventoy folks will get it sorted out presently.
(tried tcl-15.x, tcl-14.x, tcl-13.x, and tcl-12.x and ventoy brought them all up without a gui...so failure)
-
does it work properly without ventoy?
No, there is the same problem both booting with and without Ventoy, unfortunately. I flashed TinyCorePure64-15.0.iso on SanDisk 128 GB pendrive (using Rufus 4.6, GPT partition scheme and trying both "write in ISO image mode" and "write in DD image mode"). In case of ISO image mode I saw GRUB2 command line only. In case of DD image mode, I saw the boot menu (with 4 items: tc, tcw, ...).
-
Hi Vito. I have bootable USB sticks with TCL15 x86_64 that work just fine, and they go back in forth between computers with legacy bios and computers with UEFI.
My guess is that your problem stems from automated tools (e.g., Ventoy, Rufus, Balena, etc.) making assumptions about TCL, your computer (e.g., BIOS vs. UEFI), or your bootloader that are not true. But there are too many variables here to be sure what the problem is. I think ditching the automated tools and creating the bootable USB stick manually, one step at a time, is the best way.
The steps I followed to success are in this thread (first post by Juanito has everything you need for UEFI. For legacy BIOS, I discovered that the USB stick also needs a BIOS boot partition--see reply #51):
https://forum.tinycorelinux.net/index.php/topic,19364.0.html
Note that I created my bootable USB sticks in 2024, so these instructions are still valid today despite Juanito having written this in 2015!
-
I will try. However, the same TinyCorePure64-15.0.iso on SanDisk 128 GB USB-C pendrive (with Ventoy) boots successfully on another (older) laptop.
-
There's a alternative bootloader, called syslinux, in case you're interested
How to make a legacy bios/uefi dual boot usb stick with syslinux (https://forum.tinycorelinux.net/index.php/topic,20939.0.html)
BTW, when I was still a noob, I used to use Pendrive Linux (https://pendrivelinux.com/) or LinuxLive USB Creator (https://www.linuxliveusb.com/)
I haven't use them for ages, so I can't say for certain if they still do excellent job with TC.
-
Maybe newer version of GRUB solves the issue cause I got some progress by booting manually from GRUB 2.04 which is present in Ventoy 1.0.99 (by pressing <c> in a menu screen). Maybe NVMe compatibility is an issue (as it is in this newer laptop unlike the old one).
grub> set root=(loop,msdos1)
grub> linux /boot/vmlinuz64 root=/dev/sda1
grub> initrd /boot/corepure64.gz
grub> boot
-
There is the screenshot taken immediately after boot command entry - see attachment.
-
...and the final result shown in the attached screenshot. There is some error and <enter> must be pressed in order to get command prompt.
-
Hi vito
... "acpi=noirq" didn't resolve the issue, unfortunately. ...
How about acpi=off ?
-
hi vito, as per my previous reply(#19)
(tried tcl-15.x, tcl-14.x, tcl-13.x, and tcl-12.x and ventoy brought them all up without a gui...so failure)
since then i added "multivt" boot code manually after ventoy handed the boot off to the tcl boot screen and so i highlighted tcw and then manually added "multivt" bootcode so i had access to additional terminal sessions. then you can troubleshoot more easily.
somehow this version of ventoy is causing the normal tcl gui procedure to go awry and so we end up at the command prompt. on my laptop with intel graphics i was able to do the following:
tce-load -wi Xorg-7.7 xf86-video-intel graphics-6.6.8-tinycore64 flwm aterm wbar
startx
during earlier attempts when i didn't use the "xf86-video-intel" and "graphics-6.6.8-tinycore64"(just "tce-load -wi Xorg-7.7 flwm aterm wbar) and then "startx" it would just leave me at a blank black screen(this is where having "multivt" enabled comes in handy so you can just ctl-alt-f1 to see what it is doing and then ctl-alt-f2 to use another terminal session for troubleshooting)
keep us posted on your progress!
20241201-0358am-cst-usa-modified: forgot to say to start the additional terminal sessions before conducting experiments(if you don't have them started before ending up at a blank screen they might not work. as always, ymmv)
-
Hi vito
... "acpi=noirq" didn't resolve the issue, unfortunately. ...
How about acpi=off ?
acpi=off didn't solve the issue. It had some impact, though. Despite <ctrl>+<alt>+<delete> the laptop didn't reboot.