> > Hi Folks,
> > The 2023.10 RC series are now landing in F-39 and rawhide. There's
> > been the beginnings of a few enhancements.
> > least be no different than the usual process but I'd like to hear any
> > feedback.
> I have an issue on jetson-tx1 (L4T 32.7.4) with this f39 u-boot build:
> Everything operates correctly under u-boot, but then after entering
> initramfs the CPU hard lockup.
Just some follow-up about this issue. I've tested again recently (with
2023.10 GA rebased from f39 packages).
And the issue still arises with me. But it could be because of some
mess with /boot/dtb symlink and device-tree location expectation. (my
/boot/dtb wasn't updated
There was a bug with grub2 here, but it never made it to GA, of course
with updates-testing enabled by default anyone running pre freeze F-39
When I tried to report to #u-boot upstream, it's the first
that was raised (is device-tree rightly found ?).
Of course our distro patch might help
The Jetson (pre Xavier) devices won't boot without the kernel DT, the
DT provided by U-Boot has some issue around the global timer and the
kernel crashes in very early boot. It's something that I've been
meaning to look into but haven't had the time.
The problem is that in-between I've broken my micro-usb port, so
cannot update u-boot anymore on the jetson-tx1 (and I'm stuck with
fedora based u-boot 2023.07 there).
2023.07? That's still quite new.
Anyway, I don't think it's a blocker for F39 GA, so if anyone
to reproduce (or not) it is worth mentioning in the wiki.
I can reproduce, and I have been looking into it along with the issues
with the RPi4. I have currently 5 or 6 issues on my list including 3
with the RPi, these ones and possibly more. The issues for some reason
which I'm unsure about are proving very difficult to bisect which is
causing me issues around timing but overall I am hoping to get to the
bottom of them all tomorrow and a new official build done, I was
planning on replying on this thread when I have a new package for