Minimize jp6 readme

[ejgoldik]

No description provided.

[Copilot]

Pull request overview

Updates JetPack 6.0 and 6.2 README instructions to install kernel artifacts into a separate “dev” boot entry (instead of overwriting the default kernel), and removes jetson-io troubleshooting guidance to simplify the docs.

Changes:

• Add steps to place Image/DTBO artifacts under a “dev” boot path and configure extlinux.conf to boot it.
• Simplify driver install steps (remove jetson-io flow and prior troubleshooting block).
• Update overlay copy instructions to use a wildcard for multiple overlay variants.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 6 comments.

File	Description
README_JP6.2.md	Updates instructions to use a “dev” boot entry and provides an extlinux.conf example; removes jetson-io troubleshooting section.
README_JP6.0.md	Same documentation changes for JP6.0 (separate “dev” kernel path + extlinux example; remove troubleshooting section).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The overlay guidance is unclear/likely incorrect: it contains else> and references a .dtb extension, while the file examples elsewhere use .dtbo and a concrete filename. Please rewrite this bullet to clearly state the expected overlay filename(s) (e.g., single vs dual variants) and the correct extension/path that matches the earlier copy step and the extlinux example.

Suggested change

	- add the "OVERLAYS" line pointing to the required overlay "tegra234-camera-d4xx-overlay/dual/else>.dtb
	- add the "OVERLAYS" line pointing to the required overlay `.dtbo` file in `/boot/dev/` (for example, `/boot/dev/tegra234-camera-d4xx-overlay.dtbo` for a single-camera setup or `/boot/dev/tegra234-camera-d4xx-overlay-dual.dtbo` for a dual-camera setup)

[Copilot]

Same issue as JP6.2: the OVERLAYS instruction appears malformed (else>) and uses .dtb instead of .dtbo used elsewhere in the doc. Please clarify the exact overlay filename(s) and ensure the extension/path matches the copy commands and the provided extlinux.conf example.

Suggested change

	- add the "OVERLAYS" line pointing to the required overlay "tegra234-camera-d4xx-overlay/dual/else>.dtb
	- add the "OVERLAYS" line pointing to the required overlay "/boot/dev/tegra234-camera-d4xx-overlay.dtbo"

[Nir-Az]

2 things I learned so far from the last week trying to ramp up the MIPI Orin.

1. No UI display and dmesg symbols mismatch errors?

• This is due to leftovers from the previous kernel modules built against the older kernel.
  Add a step of
  sudo rm -r /lib/modules
  before
  sudo cp -r .... /lib/modules

I had to revert the changed that removed the initrd for making the device nodes to appear.

sudo depmod
sudo update-initramfs -uk 5.15.148-tegra
sudo rm -f /boot/initrd
sudo ln -s /boot/initrd.img-5.15.148-tegra /boot/initrd

With these 2 changes I now have a UI , no dmesg issues and all video devices.

Note: V4L cannot stream but this looks like an issue on my setup, will try to change HW and check next week

[ejgoldik]

"
sudo depmod
sudo update-initramfs -uk 5.15.148-tegra
sudo rm -f /boot/initrd
sudo ln -s /boot/initrd.img-5.15.148-tegra /boot/initrd
"
This is no longer part of the flow.
I believe it was removed a while ago

Regarding removing all the modules it is a bit dangerous. Probably need to consider making a backup of it first

[Nir-Az]

Since current guide cause the UI to be removed (display drivers issue) and fixing it require updating the initrd,
I think this is mandatory to the guide.

Before this PR It was there.
#309

Please consider adding this steps.
If you keep the original /lib/module and relace the kernel you had old modules with mismatch CRC and you will see in dmesg lines that say mismatch on symbol.

These steps fix it.
Of course users need to build the driver and kernel with there modified modules to align CRC match