Recent Posts

61

TCE Bugs / Re: Xfbdev-jwm-desktop bug

« Last post by neonix on March 03, 2026, 12:37:50 AM »

When I install Xfbdev-jwm-desktop.tcz in TC17 x86-64
it requires wayland.tcz and dav1d.tcz. Are those extensions are really needed?

62

General TC Talk / Re: Bulding the kernel from source and making an ISO?

« Last post by edmazing on March 02, 2026, 09:07:41 PM »

Alright having some success. I had a bit of a silly setback using fltk-1.4 when flwm_topside wants 1.3.

I ran into an issue when they system was booting up asking for

Code: [Select]

/etc/sysconfig/wbar.lst so to suppress that I figured I'd just make an empty file there, well now Wbar has vanished. I think it might be related to missing .wbar and .wbarconf in the home directory.

Edit: Apparently making xwbar.lst will do the job.

63

TCB Bugs / Re: CorePure64 v17 networking issues

« Last post by Rich on March 02, 2026, 08:16:38 PM »

Hi tzx17077
I just took a look at the TC16 and 17 x86_64 config files and noticed a
bunch of  HYPERV  options visible in TC16 but missing in TC17.

This one stood out. Does this look like what's missing:
http://tinycorelinux.net/16.x/x86_64/release/src/kernel/config-6.12.11-tinycore64

Code: [Select]

#
# Microsoft Hyper-V guest support
#
CONFIG_HYPERV=m
# CONFIG_HYPERV_VTL_MODE is not set
CONFIG_HYPERV_TIMER=y
CONFIG_HYPERV_UTILS=m
CONFIG_HYPERV_BALLOON=m
# end of Microsoft Hyper-V guest support
http://tinycorelinux.net/17.x/x86_64/release/src/kernel/config-6.18.2-tinycore64

Code: [Select]

#
# Microsoft Hyper-V guest support
#
# CONFIG_HYPERV is not set
# end of Microsoft Hyper-V guest support
Here are all of the  HYPERV  entries for both config files.
TC16:

Code: [Select]

tc@E310:~/Desktop$ grep HYPERV config-6.12.11-tinycore64
CONFIG_HYPERVISOR_GUEST=y
# CONFIG_KVM_HYPERV is not set
CONFIG_HYPERV_VSOCKETS=m
CONFIG_PCI_HYPERV=m
CONFIG_PCI_HYPERV_INTERFACE=m
CONFIG_SYS_HYPERVISOR=y
CONFIG_HYPERV_STORAGE=m
CONFIG_HYPERV_NET=m
CONFIG_HYPERV_KEYBOARD=m
# CONFIG_DRM_HYPERV is not set
CONFIG_FB_HYPERV=m
CONFIG_HID_HYPERV_MOUSE=m
CONFIG_HYPERV=m
# CONFIG_HYPERV_VTL_MODE is not set
CONFIG_HYPERV_TIMER=y
CONFIG_HYPERV_UTILS=m
CONFIG_HYPERV_BALLOON=m
CONFIG_XEN_SYS_HYPERVISOR=y
CONFIG_HYPERV_IOMMU=y
# CONFIG_HYPERV_TESTING is not set
TC17:

Code: [Select]

tc@E310:~/Desktop$ grep HYPERV config-6.18.2-tinycore64
CONFIG_HYPERVISOR_GUEST=y
# CONFIG_KVM_HYPERV is not set
CONFIG_SYS_HYPERVISOR=y
# CONFIG_HYPERV is not set
CONFIG_XEN_SYS_HYPERVISOR=y

64

TCB Bugs / Re: Module.symvers and System.map Missing for TC 17.x

« Last post by Paul_123 on March 02, 2026, 07:19:27 PM »

You definitely need them to build modules, but I forget which stage they get built.   Not sure modules_prepare is enough.

Anyway, I just uploaded them to the kernel source folder for v17

65

TCB Bugs / CorePure64 v17 networking issues

« Last post by tzx17077 on March 02, 2026, 05:10:18 PM »

Hi all,

I am running TinyCore guest VMs in different hypervisors, such as VMW, Virtualbox, Hyper-V.
All of those use the 64bit port w/o graphical desktop (CorePure64).
With the latest version I face issues with my virtual network switches for Hyper-V supervisor: TinyCore does not detect them as network cards and thus refuses to go „online“.
VMWare and Virtualbox on the other hand work fine.

Anyone else facing similiar issues with Hyper-V? Does the kernel lack the capability to support Hyper-V networking? It so, why was this not the case with the previous versions?

66

TCB Bugs / Re: Module.symvers and System.map Missing for TC 17.x

« Last post by CNK on March 02, 2026, 04:55:21 PM »

The Module.symvers file used to be useful to compile kernel modules quickly, but it seems this was dropped after linux-5.x.y.

I kind-of doubt that because I tried being cheeky and using the Module.symvers file for TC 16.x (also kernel 6.x). However when I tried to build the r8168 driver that build failed with lots of errors complaining about missing entries in Module.symvers. So it's not a solution.

It sounds like you didn't copy config-6.18.2-tinycore64 to .config and "make oldconfig" before you started?

Oh, I might have stuffed things up and overwritten .config with TC 16's Module.symvers while I was flailing around trying to find solutions. Anyway now I've got it:

Code: [Select]

$ grep tinycore .config
CONFIG_LOCALVERSION="-tinycore64"

Also I definitely downloaded it from the TC 17.x directory, not an earlier release.

I just tried again after deleting the old TC 16.x Module.symvers file and running "make clean" and it completes the "make oldconfig && make prepare && make modules_prepare" commands. But the driver build still fails complaining about no Module.symvers file:

Code: [Select]

$ make modules
[snip]
make[3]: Entering directory '/home/cnk2/r8168/r8168-8.056.02/src'
  CC [M]  r8168_n.o
  CC [M]  r8168_asf.o
  CC [M]  rtl_eeprom.o
  CC [M]  rtltool.o
  LD [M]  r8168.o
  MODPOST Module.symvers
WARNING: /home/cnk2/r8168/linux-6.18.2/Module.symvers is missing.
         Modules may not have dependencies or modversions.
         You may get many unresolved symbol errors.
         You can set KBUILD_MODPOST_WARN=1 to turn errors into warning
         if you want to proceed at your own risk.
ERROR: modpost: "napi_alloc_skb" [r8168.ko] undefined!
ERROR: modpost: "alloc_etherdev_mqs" [r8168.ko] undefined!
ERROR: modpost: "pci_save_state" [r8168.ko] undefined!
ERROR: modpost: "free_irq" [r8168.ko] undefined!
ERROR: modpost: "is_vmalloc_addr" [r8168.ko] undefined!
ERROR: modpost: "device_set_wakeup_enable" [r8168.ko] undefined!
ERROR: modpost: "__skb_pad" [r8168.ko] undefined!
ERROR: modpost: "rtnl_unlock" [r8168.ko] undefined!
ERROR: modpost: "skb_copy_bits" [r8168.ko] undefined!
ERROR: modpost: "param_ops_uint" [r8168.ko] undefined!
WARNING: modpost: suppressed 149 unresolved symbol warnings because there were too many)
make[5]: *** [/home/cnk2/r8168/linux-6.18.2/scripts/Makefile.modpost:147: Module.symvers] Error 1
make[4]: *** [/home/cnk2/r8168/linux-6.18.2/Makefile:1960: modpost] Error 2
make[3]: *** [/home/cnk2/r8168/linux-6.18.2/Makefile:248: __sub-make] Error 2
make[3]: Leaving directory '/home/cnk2/r8168/r8168-8.056.02/src'
make[2]: *** [Makefile:248: __sub-make] Error 2
make[2]: Leaving directory '/home/cnk2/r8168/linux-6.18.2'
make[1]: *** [Makefile:181: modules] Error 2
make[1]: Leaving directory '/home/cnk2/r8168/r8168-8.056.02/src'
make: *** [Makefile:41: modules] Error 2

Trying KBUILD_MODPOST_WARN=1 succeeds, so I guess maybe that's OK, but I'd be a bit surprised if the driver actually works after all the unresolved symbol warnings. It's kind of a pain to test if it doesn't because I normally run my target system headless.

Code: [Select]

$ make KBUILD_MODPOST_WARN=1 modules
make -C src/ modules
make[1]: Entering directory '/home/cnk2/r8168/r8168-8.056.02/src'
find: ‘/lib/modules/6.18.2/kernel/drivers/net/ethernet’: No such file or directory
find: ‘/lib/modules/6.18.2/kernel/drivers/net’: No such file or directory
make -C /lib/modules/6.18.2/build M=/home/cnk2/r8168/r8168-8.056.02/src modules
make[2]: Entering directory '/home/cnk2/r8168/linux-6.18.2'
make[3]: Entering directory '/home/cnk2/r8168/r8168-8.056.02/src'
  MODPOST Module.symvers
WARNING: /home/cnk2/r8168/linux-6.18.2/Module.symvers is missing.
         Modules may not have dependencies or modversions.
         You may get many unresolved symbol errors.
         You can set KBUILD_MODPOST_WARN=1 to turn errors into warning
         if you want to proceed at your own risk.
WARNING: modpost: "napi_alloc_skb" [r8168.ko] undefined!
WARNING: modpost: "alloc_etherdev_mqs" [r8168.ko] undefined!
WARNING: modpost: "pci_save_state" [r8168.ko] undefined!
WARNING: modpost: "free_irq" [r8168.ko] undefined!
WARNING: modpost: "is_vmalloc_addr" [r8168.ko] undefined!
WARNING: modpost: "device_set_wakeup_enable" [r8168.ko] undefined!
WARNING: modpost: "__skb_pad" [r8168.ko] undefined!
WARNING: modpost: "rtnl_unlock" [r8168.ko] undefined!
WARNING: modpost: "skb_copy_bits" [r8168.ko] undefined!
WARNING: modpost: "param_ops_uint" [r8168.ko] undefined!
WARNING: modpost: suppressed 149 unresolved symbol warnings because there were too many)
  CC [M]  r8168.mod.o
  CC [M]  .module-common.o
  LD [M]  r8168.ko
make[3]: Leaving directory '/home/cnk2/r8168/r8168-8.056.02/src'
make[2]: Leaving directory '/home/cnk2/r8168/linux-6.18.2'
make[1]: Leaving directory '/home/cnk2/r8168/r8168-8.056.02/src'

I guess it could be that r8168 hasn't been updated to work without Module.symvers on newer kernels. But the current kernel documentation still describes needing Module.symvers at "the MODPOST step" for building external modules.

I guess if it is still used, I could generate Module.symvers myself by doing a full kernel build. No time to try that right now though.

67

Raspberry Pi / Re: piCore TouchScreen Not Working Properly

« Last post by Paul_123 on March 02, 2026, 04:31:10 PM »

Normally udev does this for you, but in this case, the device does not properly tell the kernel that it is a multi touch device.   So you have to do it manually.   It’s a poorly built firmware in the touch controller.

68

Raspberry Pi / Re: piCore TouchScreen Not Working Properly

« Last post by lwhritner on March 02, 2026, 12:31:27 PM »

The touchscreen is now working properly! Loading the touchscreen extension and hid_multitouch resolved the issue.

Didn't realize that you needed to use sudo modprobe to load kernel modules, but doing that allowed hid_multitouch to do its thing.

Thank you very much for your help.

69

TCE Talk / Re: Source of wbar

« Last post by amplefiction on March 02, 2026, 11:17:52 AM »

Thanks Juanito and Rich

70

Raspberry Pi / Re: piCore TouchScreen Not Working Properly

« Last post by Paul_123 on March 02, 2026, 10:40:56 AM »

hid_multitouch is in the base os,  you just need to load it.  You also need the touchscreen extension.   The OS automatically loads the correct one, as long as you load touchscreen-KERNEL.tcz