New kernels

[xeno74]

Hypex,

Do you use the USB2 controller on your X1000?

Link: X1000: USB2 (EHCI) connector on the Nemo board

Cheers,
Christian

[xeno74]

Hi All,

I released the new stable long-term kernel 5.10.234 today.

New:

e5500: Support for the Renesas xHCI controller with firmware

Download: github.com

Alternative download link: linux-image-5.10.234-X1000_e5500.tar.gz

These kernels use XZ compressed kernel modules (CONFIG_MODULE_COMPRESS=y and CONFIG_MODULE_COMPRESS_XZ=y). Please test the kernel modules.

This kernel has been patched with the dpaa-v2.patch because of an issue with DPAA on Ubuntu 16.04.

It's suitable for old Linux distributions which don't work with the latest kernels for example Ubuntu 10.04.
It's also suitable if you have some issues with the latest kernels.



Please test the kernels.

Thanks,
Christian

[Hypex]

Hypex,

Do you use the USB2 controller on your X1000?

Link: X1000: USB2 (EHCI) connector on the Nemo board

Cheers,
Christian

Yes, will post in thread.

I've also been going through kernel logs. So what I wonder is where the DTB is copied from? So the kernel boots, does some setup, copies the dtb out, then restarts itself. By the looks of if the dtb is stored just above the binary space where the ELF segments are loaded in and in case of ramdisk just above ramdisk. The corrupted entry is the PCI rootbus which is fairly major.

I note in your boot line you only disable usb where as I disable both interrupts and usb as this was recommended years ago. Could this have an affect on the outcome? Another difference is you use a CF card. I never set one up so used to use USB to load from. Now days I exclusively use an FFS DOS3 volume to load kernels from. Either direct from CFE or indirect from my loader. I wonder if you see the same issue if you copied a zImage to an FFS volume and booted it from CFE?

[xeno74]

I wonder if you see the same issue if you copied a zImage to an FFS volume and booted it from CFE?

I will try it.

[xeno74]

Hi All,

I released the RC3 of kernel 6.14 today.

Download and further information: github.com

Alternative download link: linux-image-6.14.0-rc3-X1000_e5500.tar.gz (xenosoft.de)



@All
If you have a Renesas USB3 xHCI controller, then please test this controller with this kernel.

Thanks,
Christian

[musa]

Hi
I have successfully tested vmlinux-5.10.234 on Ubuntu 16.04. This time Ubuntu did not freeze. I worked on it for a while and it seemed stable. So maybe it was the kernel I used last that caused Ubuntu to freeze.
Have a nice day

[xeno74]

Hi
I have successfully tested vmlinux-5.10.234 on Ubuntu 16.04.

Great! Thanks a lot for testing!

[musa]

Hi
I have testet debian 32 trixie with vmlinux-6.14_rc3 with success.
Unfortunately both debian 32 and debian 64 are down after the last updates. X won't run. Debian 32 says something about a bug in collord
Have a nice day

[xeno74]

I have testet debian 32 trixie with vmlinux-6.14_rc3 with success.

Good to know, that it works. Thank you for testing!

Additionally thanks for reporting, that the latest Debian 32 and 64 don't work anymore after the last updates.

[Hypex]

Hi All,

I released the new stable long-term kernel 5.10.234 today.

Currently running now. Seems stable. Booted from my loader with ramdisk and it had no issues finding root PCI device info:

Code: Select all

Feb 22 03:35:35 ubuntu kernel: ioremap() called early from .pas_pci_init+0xc4/0x114. Use early_ioremap() instead
Feb 22 03:35:35 ubuntu kernel: Found PA-PXP PCI host bridge.
Feb 22 03:35:35 ubuntu kernel: PCI host bridge /pxp@0,e0000000 (primary) ranges:
Feb 22 03:35:35 ubuntu kernel:  IO 0x00000000fc800000..0x00000000fcffffff -> 0x0000000000000000
Feb 22 03:35:35 ubuntu kernel: MEM 0x0000000080000000..0x00000000e00fffff -> 0x0000000080000000 
Feb 22 03:35:35 ubuntu kernel: MEM 0x00000000fd800000..0x00000000fd800fff -> 0x00000000fd800000 
Feb 22 03:35:35 ubuntu kernel: MEM 0x0000080000000000..0x00000bffffffffff -> 0x0000080000000000 
Feb 22 03:35:35 ubuntu kernel: no ISA IO ranges or unexpected isa range, mapping 64k
Feb 22 03:35:35 ubuntu kernel: ISA bridge (early) is /pxp@0,e0000000/io-bridge@0
Feb 22 03:35:35 ubuntu kernel: ioremap() called early from .pas_setup_arch+0x44/0x60. Use early_ioremap() instead

There were some module errors about XZ. Only about bluetooth I could see. I don't have any bluetooth devices plugged in so rather harmless on my system it looks.

Code: Select all

Feb 22 03:35:38 ubuntu bluetoothd[2351]: Bluetooth daemon 4.98
Feb 22 03:35:38 ubuntu bluetoothd[2351]: Starting SDP server
Feb 22 03:35:38 ubuntu modprobe: FATAL: Could not read '/lib/modules/5.10.234-powerpc64-smp/kernel/net/bluetooth/bluetooth.ko.xz': Invalid module format
Feb 22 03:35:38 ubuntu bluetoothd[2351]: opening L2CAP socket: Address family not supported by protocol
Feb 22 03:35:38 ubuntu bluetoothd[2351]: Server initialization failed
Feb 22 03:35:38 ubuntu bluetoothd[2351]: Failed to init alert plugin
Feb 22 03:35:38 ubuntu bluetoothd[2351]: Failed to init time plugin
Feb 22 03:35:38 ubuntu bluetoothd[2351]: Failed to init proximity plugin
Feb 22 03:35:38 ubuntu modprobe: FATAL: Could not read '/lib/modules/5.10.234-powerpc64-smp/kernel/net/bluetooth/bluetooth.ko.xz': Invalid module format

I also booted the 6.14 RC2 which managed to work. But it struggled as it was waiting over a minute for devices to appear. Then the desktop managed to load. I'm struggling with Fienix with it as it has no desktop. So surviving on menu and shell. But at times I want to open a folder but can't.