Yes, but I don’t think hijacking somebody else’s question and double posting obvious log output will help the issue.
Sorry for that, but I wanted to stick with this subject because problem is connected with deploing mainstream kernel. So, what is your advice? Leave the question here or create a new question with uploading tegra30-apalis-eval.dtb on apalis problem?
Apalis T30 # run update_fdt
reading apalis_t30/tegra30-apalis-eval.dtb
29450 bytes read in 32 ms (898.4 KiB/s)
writing 730a
0 bytes written
Looks like something went wrong writing the device tree.
** Unable to read file tegra30-apalis-eval.dtb **
Without a device tree a mainline Linux kernel won’t start.
Yes, please open a new question about the device tree update issue so we can have a look at it.
Hi Marcel,
We are trying to run mainline kernel in Apalis T30. We are following your post, thanks. We have compiles, flashed the SD card and could boot. But boot hangs in between. Attached is the boot log and it always hangs at same place. Please have your comments.
Thanks and Best regards,
Don Michael.link text
Hi Don Michael
One should not hijack an old thread but rather open a new question.
That said you just have to adjust the rootfs as mainline uses a slightly different device numbering scheme. E.g. from within U-Boot just change emmcargs
as follows:
Apalis T30 # setenv emmcargs 'ip=off root=/dev/mmcblk2p2 rw,noatime rootfstype=ext3 rootwait'
Apalis T30 # saveenv
Cheers
Marcel Ziswiler
Platform Manager Embedded Linux
Hi Marcel
Sorry about that. Since it is the same question I have, thought not to create a duplicate question.
Your suggestion worked and the boot is now complete. Thank you very much.
The Links to the BSP are invalid. Could you please update them?
I have compiled the mainline kernel (4.15.7) for an Apalis iMX6, using the rootfs from the Colibri Vybrid BSP. With a few modifications I was able to get the display to work. I still am not sure why it only works with the Colibri Vybrid root file system.
What is it about the Colibri Vybrid root file system that makes this work? Specifically, could you expand on the DRM modesetting stuff? I’d like to know what elements from the Colibri Vybrid root file system are needed to support DRM/modeseting .
hi jbriede
Welcome to the Toradex Community. Please ask a new question and provide some information about your issue? Thanks.
Hm, I don’t remember where the LOADADDR of 0x82008000 above came from but usually for T30 it is really 0x80008000. At least our downstream BSPs always used that as long we still used legacy uImage (e.g. BSP 2.7 stable):
[user@host apalis-t30_bin]$ mkimage -l uImage--3.1.10+gitr0+7753763827-2.7.4-apalis-t30-20171005023218.bin
Image Name: Linux-3.1.10-2.7.4+g7753763
Created: Thu Oct 5 05:08:01 2017
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4243776 Bytes = 4144.31 KiB = 4.05 MiB
Load Address: 80008000
Entry Point: 80008000
Nowadays, one may just want to use zImage instead.
Colibri T30 1GB it
Colibri Eval board
Linux colibri-t30 4.14.183- 2.8.7
Hi we are using the mainline linux kernel Yocto recipe originally targeted for apalis to try and use a newer kernel. We don’t care about the proprieretary Nvidia video driver stack… we want to use a newer kernel so that we can use newer enjoy better kernel support for things like our network stack.
So we followed your good instructions here and we were able to get a 5.10 mainline kernel (which worked) but I currently don’t know how to integrate that into our yocto flow. Especially using BSP 2.8.7 (yocto rocko version) and thus I just tweaked the apalis t30 recipe to compile for colibri t30.
With me so far?
LXDM crashes with the rootfs produced for the Colibri T30 (made by the angstrom-lxde-image recipe from the BSP 2.8.7)
" using DRM/modesetting by default." what does this mean? how do we get lxdm running on a 4.14 kernel , what do we need to change in the rootfs to make that happen?
I know we are off the beaten path here, but we have a ton of Colibri T30 modules and I need to find a way to try and make linux do all of the things we need to do. It would really help things if I could integrate a new kernel. I tried briefly to use a linux-yocto kernel recipe for 5.10.y (but was rather stumped on to integrate the standard recipe)
Please help, Thanks