Tiny Core Base > Alpha Releases

Tiny Core 16.0 Alpha 1 Testing

<< < (5/16) > >>

Leee:

--- Quote from: Juanito on February 07, 2025, 03:57:43 AM ---..but: http://repo.tinycorelinux.net/16.x/x86_64/tcz/abiword.tcz.dep

contains:
--- Code: ---wv.tcz
enchant2.tcz
goffice.tcz
redland.tcz
libical3.tcz
glibc_gconv.tcz
adwaita-icon-theme.tcz
--- End code ---

--- End quote ---
Hmmmm.... Looks like tce-load did not retrieve abiword.tcz.dep - there likely was some error message that I didn't notice as I had many distractions at the time.

Apparently everything else listed in abiword.tcz.dep had already been downloaded as deps of other things, so the fact that there was no dep file at all didn't jump out at me.

Rich:
Hi Knoppix1337
Paul_123 compiled a kernel that enabled the Boot Printk debugging option.
You can find it here:
http://tinycorelinux.net/16.x/x86/debug/

I tried it out by replacing quiet with:

--- Code: ---boot_delay=200
--- End code ---

The  Booting kernel  message displayed for about 2 or 3 minutes, probably
processing the early printk messages that don't normally get printed.
Then the regular printk messages started and they scrolled at a comfortable
rate to read.

Knoppix1337:
I previously tried all kinds of cheatcodes including acpi=off noapic nolapic. I didn't know about nomodule but that had no effect either.

I tried the printk kernel, this machine is only 1ghz, so it waited alot longer than 2-3min at booting kernel, thanks for the warning.

It slowly went through all the messages, and IT BOOTED FINE!
So I tried it without the boot delay=200 and without loglevel=7, and it still booted fine.
Then I added sleep 13 and reboot to bootlocal.sh and left it for like 5 hours and it was still going.

So it works, but we still don't know why or what the issue was.

I was previously looking through the boot sequence code, and although I used the waitusb=13 cheatcode, the message from the bootcode never showed up showing that it was actually waiting. It's the only thing out of the ordinary that I noticed.

curaga:
It's a kernel bug of some kind, but it will be hard to track down without messages, if you can't compile the kernel and try to bisect where it broke down.

Rich:
Hi Knoppix1337
Since it now boots, execute this:

--- Code: ---dmesg > dmesg.txt
--- End code ---
and attach the file to your next post. Maybe something
will stand out.

Navigation

[0] Message Index

[#] Next page

[*] Previous page