Ubuntu cannot see a formatted microSD card on BeagleV Fire
How to reproduce:
- Download the Ubuntu SD card image from https://git.beagleboard.org/beaglev-fire/BeagleV-Fire-ubuntu/-/jobs/51438/artifacts/download?file_type=archive
- Flash the image onto the BeagleV Fire with Balena Etcher. I did this on Windows 11 and Etcher reported a successful flash.
- Put a formatted microSD card in the slot on the BeagleV Fire.
- Boot up the BeagleV Fire and log in. User = beagle and password = temppwd.
- Do an lsblk on the console:
beagle@BeagleV:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
mmcblk0 179:0 0 14.6G 0 disk
├─mmcblk0p1 179:1 0 684K 0 part
├─mmcblk0p2 179:2 0 128M 0 part /boot/firmware
└─mmcblk0p3 179:3 0 14.5G 0 part /
mmcblk0boot0 179:256 0 4M 1 disk
mmcblk0boot1 179:512 0 4M 1 diskbeagle@BeagleV:~$-- AlgoCompSynth by znmeb https://universeodon.com/deck/@AlgoCompSynth
I don't have the hand muscles for strongly-typed languages.
Sent with Proton Mail secure email.
Activity
@RobertCNelson:
This issue relates to a fix from me that went in some 6 months ago.beagleboard/BeagleBoard-DeviceTrees!102 (merged)
As I wrote on the forum https://forum.beagleboard.org/t/is-there-any-way-to-mount-an-sd-card-in-a-beaglev-fire-running-trixie/41121/6?u=lranders, I tried to revert the change by "quick-fixing" the Devicetree in u-boot, but to no avail...
It just triggers an anomaly in the kernel and it fails to find a rootfs completely.
So does this issue belong in the device tree repo?
...
-- How many people can stand on the shoulders of a giant before the giant collapses?
Sent with Proton Mail secure email.
On Thursday, February 13th, 2025 at 2:11 AM, Lars Randers (@lranders) gitlab@openbeagle.org wrote:
Forum | Documentation | Website | Blog
@RobertCNelson: This issue relates to a fix from me that went in some 6 months ago.
beagleboard/BeagleBoard-DeviceTrees!102 (merged)
As I wrote on the forum https://forum.beagleboard.org/t/is-there-any-way-to-mount-an-sd-card-in-a-beaglev-fire-running-trixie/41121/6?u=lranders, I tried to revert the change by "quick-fixing" the Devicetree in u-boot, but to no avail...
It just triggers an anomaly in the kernel and it fails to find a rootfs completely.
— Reply to this email directly or view it on GitLab. You're receiving this email because of your account on openbeagle.org. Unsubscribe from this thread · Manage all notifications · Help
Open hardware computers for makers, educators and professionals
