WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Re: Tiny Core v17.0 upgrade issues  (Read 11773 times)

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 12801
Re: Tiny Core v17.0 upgrade issues
« Reply #165 on: May 28, 2026, 02:45:43 PM »
Hi Stefann
Code: [Select]
tce-load -wi advcomp

Offline Stefann

  • Wiki Author
  • Full Member
  • *****
  • Posts: 214
Re: Tiny Core v17.0 upgrade issues
« Reply #166 on: May 28, 2026, 03:28:25 PM »
Hi Stefann
Install  advcomp.tcz.
Almost!…… This worked:
Code: [Select]
tc@hp510:~$ tce-load -wi advcomp.tczBut thanks for the tcz name. I would not have found that otherwise

But no luck…
Code: [Select]
tc@hp510:/krubo/work/TC/linux-6.18.28/arch/x86/boot$ advdef -z4 bzImage
File type not supported on bzImage [at void convert_inplace(const string&):redef.cc:498]

Note…
Probably no activity anymore today.
As said I’m on a trip.
Social obligations now and sleep after that (living in Europe/netherlands)





« Last Edit: May 28, 2026, 03:31:27 PM by Stefann »

Offline Paul_123

  • Administrator
  • Hero Member
  • *****
  • Posts: 1569
Re: Re: Tiny Core v17.0 upgrade issues
« Reply #167 on: May 28, 2026, 03:35:46 PM »
It wants the file name to end in .gz    But if you did not have advcomp.tcz installed when compiling the kernel, then it did not get fully compressed.

With advcomp installed just remove the old bzImage from arch/x86/boot.    Then run "make bzImage" again

It should go faster as it should not have to recompile most of the code from the last run.

Offline Stefann

  • Wiki Author
  • Full Member
  • *****
  • Posts: 214
Re: Re: Tiny Core v17.0 upgrade issues
« Reply #168 on: May 28, 2026, 03:47:22 PM »
It wants the file name to end in .gz    But if you did not have advcomp.tcz installed when compiling the kernel, then it did not get fully compressed.

With advcomp installed just remove the old bzImage from arch/x86/boot.    Then run "make bzImage" again

It should go faster as it should not have to recompile most of the code from the last run.


Done, but not really different size

Code: [Select]
tc@hp510:/krubo/work/TC/linux-6.18.28/arch/x86/boot$ ls -l bz*
-rw-r--r--    1 tc       staff      6312448 May 28 21:43 bzImage

Ehh… I get in social trouble if I spend more time on this now :-)
Any input will be followed up tomorrow


Offline Paul_123

  • Administrator
  • Hero Member
  • *****
  • Posts: 1569
Re: Re: Tiny Core v17.0 upgrade issues
« Reply #169 on: May 29, 2026, 07:53:18 PM »
Lets look at compressed and uncompressed kernel.  Does vmlinux.bin match your build?

Code: [Select]
tc@Devel:~/linux-6.18.28/arch/x86/boot/compressed$ ls -l vmlinux*
-rwxr-xr-x 1 tc staff  6107368 May 29 23:38 vmlinux
-rwxr-xr-x 1 tc staff 12469728 May 29 23:38 vmlinux.bin
-rw-r--r-- 1 tc staff  6046727 May 29 23:38 vmlinux.bin.gz
-rw-r--r-- 1 tc staff     3077 May 29 23:38 vmlinux.lds
-rw-rw-r-- 1 tc staff     2308 May  8 06:40 vmlinux.lds.S
-rw-r--r-- 1 tc staff   666652 May 29 23:38 vmlinux.relocs


Offline Stefann

  • Wiki Author
  • Full Member
  • *****
  • Posts: 214
Re: Tiny Core v17.0 upgrade issues
« Reply #170 on: May 30, 2026, 04:52:01 AM »
Here you go…
Looks like you are right (but please check, I don’t know whether I compare the correct files)

Compressed vmlinux and vmlinux.bin.gz are different
But uncompressed other files have same size.

That’s good!
If it’s the compressing I doubt that that would cause the crashing

Code: [Select]
tc@hp510:/krubo/work/TC/linux-6.18.28/arch/x86/boot/compressed$ ls -l vm*
-rwxr-xr-x    1 tc       staff      6308072 May 27 12:42 vmlinux
-rwxr-xr-x    1 tc       staff     12469728 May 27 12:42 vmlinux.bin
-rw-r--r--    1 tc       staff      6248050 May 27 12:42 vmlinux.bin.gz
-rw-r--r--    1 tc       staff         3077 May 27 12:42 vmlinux.lds
-rw-r--r--    1 tc       staff         2308 May  8 08:40 vmlinux.lds.S
-rw-r--r--    1 tc       staff       666652 May 27 12:42 vmlinux.relocs

On the crashing…
As said I’m now on a trip AND have a major 1wire hardware breakdown to fix on return.
So… expect things to go a little bit slower…

With that said…. I will more thorough test whether recompiled kernel with usb-serial-6.18.2-tinycore.tcz works.
If indeed my “kernel making” is identical to your “kernel making” than my custom kernel should be identical to the published kernel and should crash. In that case the crashing is related to usb-serial “included in kernel versus by kext”.
That is entirely possible because I included only a few modules in the kernel while the usb-serial-6.18.2-tinycore.tcz has much more.