Tiny Core Base > TCB Q&A Forum

AMD K6-2 166Mhz, 512MB ram, desktop - TC11.1 runs fine TC12 fails.

(1/15) > >>

gadget42:
AMD K6-2 166Mhz, 512MB ram, desktop -  TC11.1 runs fine TC12 fails.

TC11.1 uses 5.4.3 kernel (i586)
TC12.0 uses 5.10.3 kernel (i686)

Have searched the forum but didn't see anything specific to this issue.

This machine is the oldest in the collection and the "canary in the coal mine" regarding operating systems.

What do I need to do/get to compile the newer kernel to still be usable with our older machines? Thanks!

Rich:
Hi gadget42
TC12 fails isn't much to go on. Perhaps if you provide a more thorough description of what is happening we can
figure out the problem.

What type of media are you booting from?
If you are booting from a USB device, did you use the tc-install utility or a 3rd party program? Did you include the waitusb
boot code?
Are you seeing any error messages?
Does it get to a command prompt?

gadget42:
attempting to boot TC12 using a proven cd-r and get this on screen:

Loading /boot/vmlinuz.......
Loading /boot/core.gz............
Wrong EFI loader signature.
early console in extract_kernel
input_data: 0x0071d0ae
input_len: 0x0049a1d1
output: 0x00100000
output_len: 0x009be788
kernel_total_size: 0x00ad4000
needed_size: 0x00ad4000

Decompressing Linux... Parsing ELF... No relocation needed... done.
Booting the kernel.
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
Kernel Offset: disabled
Rebooting in 60 seconds..
_

*and it stops there until the power switch is turned off...

during this testing the hard drive with Win3.1/Win3.11/TC11.1 is removed.

thanks!

Rich:
Hi gadget42
A couple of other forum members have had the same issue:
http://forum.tinycorelinux.net/index.php/topic,25011.0.html
http://forum.tinycorelinux.net/index.php/topic,25081.0.html

Try the following boot codes one at a time to see if they make things any better:

--- Code: ---acpi=off  pci=noacpi  acpi=noirq  pnpacpi=off  noapic  nolapic
--- End code ---

gadget42:
Hi Rich, read those forum posts and tried the boot codes(yes, one at a time) but nothing has changed so far.

adding "debug" boot code gave much additional "verbosity" and browsing through the paused digital camera
video footage revealed the following traps:

traps: modprobe[84] trap invalid opcode ip:b7f34081 sp:bf94447c error:0 in ld-2.32.so[b7f1d000+18000]

traps: modprobe[85] trap invalid opcode ip:b7f53081 sp:bfadf3ec error:0 in ld-2.32.so[b7f3c000+18000]

traps: init[1] trap invalid opcode ip:b7ef5081 sp:bfa66acc error:0 in ld-2.32.so[b7ede000+18000]

also read about seemingly similar issues others were having:

https://forums.gentoo.org/viewtopic-t-1089838-start-0.html

https://unix.stackexchange.com/questions/448937/is-ld-so-an-executable

http://forum.tinycorelinux.net/index.php?topic=21272.0

Thanks!

Navigation

[0] Message Index

[#] Next page