I can see the partition table layout (and mount partitions on my old laptop) listed|690x468
both laptops are running Linux Mint 20 x64.
I suspect that I have installed packages on my old laptop that mean I can see/read the filesystems that I need to install on my new laptop. please help!
edit2add
I thought perhaps it was somehow connected to the SDK Manager so downloaded/installed it but still cannot view/mount the partitions. :(
Regardless of type of filesystem and regardless of partition types, any memory using either the older BIOS scheme or UEFI schema should show the partitions. What do you see if you use the following to find information on the SD card? I am pretending the card is “/dev/mmcblk1”, but substitute for your case (e.g., if it shows up as “/dev/sdb”, then use that…you can monitor “dmesg --follow”, and view what shows up as you insert the card):
fdisk -l /dev/mmcblk1
sudo gdisk -l /dev/mmcblk1
Do those commands work on the laptop which sees the partitions in your GUI app? Do those same commands show up differently on the other laptop?
From what I can tell there are hardware failures on the new laptop. The reason the SD card could not succeed was probably not due to the SD card itself since it works on the old laptop. Regardless, there may be some filesystem inconsistencies on the SD due to failures while testing.
There are a number of reasons why this could fail on the new laptop. One is simply due to lack of correct (and updated) drivers or firmware. I have no way to speculate on specific details, but you might describe on the new laptop how the SD card is plugged in. For example, through a HUB or directly to an integrated reader. If you have an external reader using USB, then you might want to describe this as well. Also, is it correct that the new laptop is using Ubuntu 18.04?
the Reader is an integrated type, made by Alcor (model 6625) for which the drivers are integrated into kernel 5.6 upwards (I have installed kernel 5.8)
I had already come to the conclusion that it was kernel related, rather than hardware, or rather I am sure that the hardware is working because when I dual boot into Windows, I get 14 popups saying “this drive needs formatting before it can be used” (or whatever the wording is, but I am sure you know the popup I mean) which means that Windows can see the partition table but obv. can’t read *nix filesystems.
In my dmesg posting, I count 14 instances of mmcblk0: recovery failed! too
I’ve had to reinstall windows on my new laptop due to an issue with cyberpunk 2077 and still need to repair grub before I can boot into Linux but before I did so, I flashed firmware vers20 onto my new laptop (I was running vers13 that shipped with the machine)
Maybe that will help, I will report back
edit 2add
I get the same problem with my 32Gb sdcard too. So I know it isn;t due to my 128Gb card not being supportted/read due to its size
Yes, you are correct. I said “hardware”, but what I should have said is that “the hardware does not work, and likely this is due to driver or firmware missing” (and driver is part of the kernel).
You are also correct that Windows has no understanding of the filesystems on the SD card. This is not a problem, and if you format the card, then you’ll end up erasing part of your Jetson’s operating system. Just tell it to not format.
Failure to recover can be either a failure of the hardware to read/write correctly, or it can be due to a very badly mangled filesystem. Let us know what happens after the laptop repairs are made.
yes, thank you. I am aware of the limitations regarding windows and ext2/3/4 (edit2add - Linux filesystems in general) file systems and had no intention of formatting the partitions. It was just an indication that the hardware is working under windows so the issue was with Nix.
I have since been doing a lot more reading and I am not the only person having difficulties with this particular model of card reader.
It does mean that I will need to do all my flashing/chrooting from my old (lenovo w520) laptop rather than my shiny new one :(
Well, until i learn how to recompile my kernel, that is. I have only ever tried this once and it didn;t work well (approx 20 years ago, on slackware 10)
your input has been appreciated though.