Use the last linux kernel on piCore arm64

[Juanito]

So why are you compiling the RPi kernel?

[cosminbro]

So why are you compiling the RPi kernel?

Because I want the last linux kernel. I saw there are more drivers included, especially for wireless lan adapters.

For the moment it seems the main problem is with modules archive. How can I compile a modules archive similar to this http://tinycorelinux.net/13.x/aarch64/releases/RPi/src/kernel/modules-5.10.77-piCore-v8.tar.xz, for another linux kernel version?

[Juanito]

The modules archive is not the main issue.

If you wish to update the kernel for piCore64-13.1, you will need to replace kernel51077v8.img and modules-5.10.77-piCore-v8.gz and modify rootfs-piCore64-13.1.gz

[cosminbro]

The modules archive is not the main issue.

If you wish to update the kernel for piCore64-13.1, you will need to replace kernel51077v8.img and modules-5.10.77-piCore-v8.gz and modify rootfs-piCore64-13.1.gz

I manage to replace kernel, but no modules-5.10.77-piCore-v8.gz

[cosminbro]

Modules need to be compiled for the new kernel, how can I do this?

[Juanito]

The modules are at: https://github.com/raspberrypi/firmware/tree/next/modules/6.1.8-v8%2B

[cosminbro]

The modules are at: https://github.com/raspberrypi/firmware/tree/next/modules/6.1.8-v8%2B

I do this and at boot it gave me the error message: modprobe: can’t change to folder 6.1.8-v8+

[Paul_123]

Then you are not constructing your initrd files correctly.

piCore we use 2 initrd files that are concatonated together by the RPI firmware.

Here are a couple of old threads that show the basic process of replacing the kernel modules and reconstructing the initrd.

http://forum.tinycorelinux.net/index.php/topic,14634.msg89051.html#msg89051
http://forum.tinycorelinux.net/index.php/topic,14634.msg88856.html#msg88856

[cosminbro]

Thanks, I manage to boot to 6.1.8 arm64 linux kernel, starting from rootfs file from arm64 picore 13.0

LAN network is working, it seems to load all modules.

Now, another problem, when I try to install tcz modules, some worked, some are compiled for specific kernel from 13.x distribution and doesn't work -> they need modulename6.1.8v8+.tcz modules

Can I use the current tcz from last tiny linux repo, download to local and rename to match the new required name, or it must be compiled against new 6.1.8 kernel?

[Paul_123]

You need to recreate the extensions with modules from the same kernel version.  Assuming you downloaded the precompiled kernel from raspberry pi, just use those same modules to build the extensions.

[elcouz]

cosminbro, I am in the same state as you for the wireless adapter. I need 802.11ac for the deployment, MT7610u is the only one I know supported with kernel 5.10.77.
I wish Picore was on 6.12 as it support now Realtek ones but as the other stated it seems not stable.

Were you able to switch to the new kernel? I like doing programming and some linux configuration but this is kind out of my league.

If not I am patiently waiting for Picore 14.0 on kernel 6.12 


Thanks

[curaga]

https://wireless.wiki.kernel.org/en/users/drivers/ath10k

Why not use Atheros stuff? They're generally good quality, and that says it was in well before 5.10.

[elcouz]

https://wireless.wiki.kernel.org/en/users/drivers/ath10k

Why not use Atheros stuff? They're generally good quality, and that says it was in well before 5.10.

They are hard to find ... AP are 802.11ac only, if it was possible with 2.4ghz (n) I wouldn't even write here. Internal Pi Broadcom wireless would be the best choice driver wise for support but it is too weak to use in an industrial environment.

EDIT: I've check there is limited to none USB support for ath10k driver.

I had some good driver success with Linksys AE6000 ac adapter (MT7610u) but range is not enough. (Getting unstable 6 mbit connection on 802.11ac with tons of dropped packets)


Also I noticed wifi.sh does not work with too many APs. With more than 1000's SSID on my work site to list,  it goes out of bound.  But that is an extreme case

[Paul_123]

I wouldn't hold my breath for the realtek junk, The only drivers that seem to work, are out of tree, and I'm not going to go down that rabbit hole.

The mediatek product/drivers are pretty stable.

We are working on piCore64/14 but it will still be a bit.  I don't start doing kernel work, until raspberry pi switches their branches.  Which they have done in the last couple of weeks.

[elcouz]

I wouldn't hold my breath for the realtek junk, The only drivers that seem to work, are out of tree, and I'm not going to go down that rabbit hole.

The mediatek product/drivers are pretty stable.

We are working on piCore64/14 but it will still be a bit.  I don't start doing kernel work, until raspberry pi switches their branches.  Which they have done in the last couple of weeks.

I fully agree with you Paul, but the lack of choice is really tough. I bought 5 wifi adapter on amazon only to find out all of them are Realtek ones. This is really a gamble as 99% don't bother to disclose what is the chipset inside. There is only little choice for the MT7610u.

I know this is the fault of Realtek to not give a damn about Linux but if it is a pain for us that can work with Tinycore imagine for a simple end user to figure out most things he buys don't work with Linux.

So far what I've found on MT7610u
-Linksys AE6000 perfectly works in a house environment , signal strength suffer in noisy/crowded environment [Available in Canada]
-Panda Wireless PAU0B [Not available in Canada] I'll try to import but it is triple the price 60USD
-Alfa Wireless AWUS036ACHM [Not available in Canada] Cost prohibitive 100USD to import