My partner and I both have digital cameras. Hers is a Canon EOS Rebel-T5, and mine is an Olympus Tough TG-6. Both cameras will create subdirectories within the /DCIM/ folder, formatted as 10*CANON or 10*OLYMP. We've shared SD cards on occasion, and neither camera has had any issues with just creating a new directory to match the current camera; e.g., one SD has /DCIM/100CANON ... /DCIM/101OLYMP, etc.

There is a highly unusual issue going on with one of the cards. It is a 64 GB [pro]master, Code 2145. It is well-used, with probably over 10,000 photos on it from my Olympus (that are backed up), but there is still plenty of room for pictures. When using this card in particular in her Canon, we have noticed that it writes photos without error, but retrieving and reading the photos on the display is terribly laggy and the camera expends a lot of energy "thinking" with the red indicator light. However, with patience, we are able to view any photos that are produced with this camera. The "photo#/total" display at top (e.g. 4/100; 5/8979) is really screwy and the second number changes often, perhaps as it reads from different directories.

ISSUE:

When I load this SD into my computer, I am only able to recognize Olympus subdirectories. There is no evidence of a Canon writing anything onto this disk, not even any of the other data directories it will normally create outside of /DCIM/. Entering the SD through CLI and using commands like /ls -a prove fruitless. Where on earth are these photos? What other options do I have in trying to attain these images?

This post idea was inspired by a recent post by Guenther_Amanita@feddit.de in this community.

I have been a Windows user for my entire life. I recall having an iMac in my bedroom as a small boy, maybe 7-8, playing random offline games on it, but aside from that, my experience growing up was with Windows 98, XP, Vista, 8 and 10. I wouldn't say I was ever a "power user" per se, although I could do several tasks that were more technical if needed, like locating driver files, updating .dlls, configuring compatibility settings, etc. I think being a good Googler made me seem more capable to my family than I really was, and I'm sure a lot of people here would share my experience!

With the impending sundowning of Windows 10, an OS that I "begrudgingly accepted" (rather than actually enjoyed using, as with Vista), and realizing that 11 was only going to bring more ads, force-installed applications, background processes that were nigh-impossible to disable without a lot of tomfoolery, AI bullshit and general bloat, I figured that I would try dual-booting Ubuntu, installing it on a partition of my storage HDD. Windows did not want to play ball, no matter how much I begged and pleaded and bargained, and eventually I was met at a point where I had to decide what to do going forward. My system was just not behaving the way I wanted to with two OSes ("This town ain't big enough for the both of us"), and figured,

Oh, what the hell. I'll primary Ubuntu and when I need to use Windows I'll run it on a thumb drive or something.

Well, it's been several weeks now and, even with a couple bumps along the way, I have not booted into Windows once since the switchover. How many of you had a similar experience? I was frankly a bit scared of CLI and thinking that I was going to brick my PC before I even had a chance to use it, so I kept all my personal files safely tucked away in a removed HDD until the break-in process was relatively complete. As time has gone on, I've gotten comfortable enough to have a backed up copy of my files on here, and every new program I go to install that I used on Windows has worked swimmingly on Linux.

I can only thank the helpful, enthusiastic people here in the Linux community for making my experience so smooth. It's rare you encounter a group of people where you can post what is ostensibly a stupid question, and be pummeled with dozens of well-formed, thoughtful, detailed responses to the question. There's very little of that infamous grandiosity and self-righteousness that I've heard runs rampant in the Linux world, and maybe Lemmings are just more prone to being helpful than the wider internet, but for what it's worth, I appreciate everything you all have done here so far.

I feel so much more capable as a computer user with Linux than I ever did on Windows. I'm automating tasks, I'm fine-tuning network drivers, I'm getting in the weeds of file architecture, and it's all been a real blast to learn about. I actually feel a desire to learn so that I can help others have a similar experience to what I had coming into this.

Any and all help would be so greatly appreciated. I've been battling with my laptop to be able to dual-boot Ubuntu Cinnamon and Windows 10 for about four days now. I've probably gone down five or six different rabbit-holes of troubleshooting, GRUB command-line fun, reinstalling and updating the BIOS, trying and failing to deal with VMX and locked NVram. As of now, my system boot-loops and fails to run Windows, but paradoxically I am able to get Ubuntu running, which is what I am using now.

I'll try to provide as much relevant information here as I can:

• Device: HP ZBook 17, gen 6
• Primary OS: Windows 10 Home
• Linux distro: Ubuntu Cinnamon 23.10
• Ubuntu location: /dev/sda3
• grub-install --version = 2.12~rc1-10ubuntu4
• boot-repair Boot-info summary: https://paste.ubuntu.com/p/rxZ3D5GtpP/
• I'm more than happy to provide more information as it's requested.

As of now, I am unable to run Windows through the BIOS. If I run via the dedicated SSD as I normally do, it boot-loops, and if I try to go through any other drives it just tells me I need to install an OS. I am currently able to run Ubuntu, but only by going through the following process:

1. Startup menu
2. Boot configuration
3. Boot from EFI > Ubuntu > shimx64.efi

At this point, I am happy with two outcomes to this scenario:

1. I am able to run my laptop with Windows 10 as the primary OS, with the ability to dual-boot to Ubuntu Cinnamon 23.10.
2. Assuming option 1 is impossible/requires a Herculean amount of work to pull off from this state, I am willing to scrub Windows 10 from my laptop and move forward with Cinnamon as my daily driver, though I am rather inexperienced in it. I can learn to move forward as I need to and run a VM or WINE for any Windows-specific processes I still need to do. But I would rather keep this option as my dead man's switch.

"Stronger" hearts typically have a resting pump rate lower than that of weaker or less healthy ones. A healthy, athletic male might have a resting BPM of 60, while an otherwise healthy but post-partem female could be closer to 90.

Would both of these hearts expend the same energy pumping 120 BPM? Would the healthier heart be theoretically expending more as it is acting in double-time, or would the weaker one be working harder as it is already inefficient at pumping blood?

I just installed Ubuntu 22.04.3 LTS (Cinnamon) on an empty laptop a couple days ago and have been experimenting a lot. I'm coming from being a Windows user since I was just a little kid playing old DOS games on my grandpa's Win-98 PC back in around 2000. My daily driver is currently running Windows 10 but I am pretty adamant on not going with Win-11. I've been wanting to experiment with Linux for a while and Cinnamon so far seems like a lot of fun to navigate. Terminal is amazing. The fact that you can custom-write keyboard commands that can be hand-tailored to individual programs on your computer via the OS... that's powerful.

I have not tried running WINE yet but I plan on doing so soon. I also have not done much of anything, honestly, except for learning how to search for programs with gnome-software --search=. I have also used sudo a couple times to download software here and there, but I know I am not tackling this in as systematic of a way as I ought to be to really figure this machine out.

What are some really important basic commands I can use to start branching out into Terminal command structures and learning more about how I can edit and customize my computer? And if Cinnamon has shortfalls or weaknesses that I may run into eventually, what are some good alternative distros that I could leapfrog to eventually? I do not have any coding experience (currently), but I do consider myself a semi-power-user on Windows, having messed with CMD many times and digging through all the damn menus to access drivers and alter ports.