<tuxd3v>
but the kernel never starts... it his olding there for half a day, and kernel still not booting..
<Jin^eLD>
tuxd3v: are you sure you have the "right" kenrel for this device and the correct ftd? there's no point to wait half a day, it obviously does not work
<Jin^eLD>
I'd also check the boot arguments
<Jin^eLD>
are you passing the riht serial option?
<Jin^eLD>
maybe the kernel actually does start, but fails to mount your rootfs due to wront bootargs
<Jin^eLD>
with the wrong serial setting you might not see printk output
<tuxd3v>
I was waiting maybe ddr timmins to slow, what because of that, that I waited all night and still not booting
<tuxd3v>
I am using Mainline kernel 5.6-rc6
<tuxd3v>
the fdt is the 'rk3399-rock-pi-4.dtb'
<tuxd3v>
because its a rockpi4A
<Jin^eLD>
I am not familiar with the rockpi, just giving you a few pointers on where to look...
<tuxd3v>
I don't know if dtb changed between RockPI versions, Rockpi4A or RockPi4B
<tuxd3v>
I assume they are the same for the same peripherals
<tuxd3v>
Jin^eLD, thankyou for your help
<tuxd3v>
Indeed it could be
<Jin^eLD>
I'd first make sure that your serial settings are correct
<Jin^eLD>
maybe you don't see printk's and its actually starting
<Jin^eLD>
lots of console settings there, I'd double check if they are correct
<Jin^eLD>
you could also add a panic parameter so it automatically reboots if it can't mount the rootfs, I dont remember the exact name
<Jin^eLD>
but this way you could kind of check if that is indeed the problem, even if you don't get the console going
<tuxd3v>
panic=timer
<Jin^eLD>
right
<tuxd3v>
I believe
<Jin^eLD>
I never remember :) but you get the idea
<Jin^eLD>
if it reboots you'd know the kernel actually started
<Jin^eLD>
and thatn your root device options are probably wrong
<tuxd3v>
It took me a day of experimented to come to this..previously it doesn't even recognized the sdcard
<tuxd3v>
now I changed to another sdcard
<tuxd3v>
serial should be wrong..
<Esmil>
tuxd3v: if you're using the serial console you can just leave out any console= arguments. ttyS0 is set as the default console in the fdt. i guess you just need to add console=tty1 if you want something on a screen at boot
<Esmil>
sorry, ttyS2 is set as the default
<Esmil>
that's the proper name in upstream kernels, not ttyFIQ
<tuxd3v>
I will try that, I don't know were I saw ttyFIQ
<Jin^eLD>
I am not sure if it makes sense to bother with boot scripts at this point, I'd try to get it up manually from uboots console in the simplies way possible, checking if each step actually worked
<Jin^eLD>
*simpliest
<tuxd3v>
I don't know how to stop at u-boot prompt :S
<tuxd3v>
maybe u-boot needs a special .config file to build it..
<Jin^eLD>
if it does not have a counter, still try pressing any key repeatedly in the serial console right after powering up the board, i.e. when you see that u-boot is loading