That is what is wrong with the safe-dd script
That \r is a carriage return.
That means the script is a DOS text file.
You need to convert it to a Unix text file
See my reply in your new topic
So plain dd works
That proves the problem is the script, not your parameters
Well done
Another warning:
If you do use plain dd, be very carefull that you get the of= parameter correct!
First, Garuda’s Arch-based, and I don’t use their flagship, Dragonized, I use their Garuda-KDE-Lite release. It starts out with a minimal number of app preinstalled, and a minimalist implementation of KDE’s Plasma. Then I got to add whatever GNU/Linux/KDE software I want, and over time, I’ve been customizing it to suit my wants and needs. At some point, I think I’ll write up what I’ve done to make the system work like I want (nothing really big or complex, just little, simple things for the most part), so, perhaps what I’ve done may help others.
Sounds like a lot of work getting a system you want from minimum. I attack from other end where everything is installed and i remove the stuff i dont want.
The truth is that I got curious about Garuda from a review here on It’sFOSS, but I’m not a fan of the looks of their flagship Dragonized, and I have always preferred the KDE (Plasma) desktop, so I tried out their Garuda-KDE-Lite flavor. It gives me a clean, non-cluttered desktop, that I can customize to my tastes, and I’ve really come to appreciate the GUI-centric utilities (scripts) Garuda has provided for system management, while at the same time, I’m learning a lot about working with the CLI. Garuda has all the fundamental stability I can ask for from their Arch base, and as I’ve used it, I’ve found that it just works for me. I also have the xfce flavor on my older laptop, and I really like their implementation of that DE. With just a bit of modification, I’ve been able to make it look and feel surprisingly similar to my Plasma DE here on my primary laptop. I suppose I’ve become a fan of how Garuda has implemented GNU/Linux in general. All-in-all, it just fits for me.
I’ve worked with distros that I have to dump a lot of stuff from, and a few that take minimalism to an extreme, and I almost have to build the system up from nearly nothing. Garuda doesn’t fit anywhere near either extreme. At first boot, after the Welcome script helped me update everything, I got the opportunity to install software from nearly every category there is, so I suppose it comes with as much, or as little as I want it to. While initially, it looked as if the Welcome app (script) did the system update, and setup, I later discovered that there is an app (script) named Garuda Update, and another named Garuda Setup. The Welcome app called these two scripts to do their jobs following first boot. I now use an alias in .bashrc to update the system from the terminal, using a custom command ‘upd’. I suppose one of the things I like best about Garuda is that while they provide all the system maintenance/configuration tools I could ever need, they let me decide how the system works, and how I want to use it. The dev team seems to have kept in mind the fundamental GNU/Linux principle of freedom, in that the user should be free to decide how the system should look, feel, and work. There are a lot of distributions I’ve tried that don’t do that.
That is one important point about FOSS.
The other is the benefits of open source… not so obvious but equally important.
What open source facilitates is … if someone ceases to maintain an app or a distro, someone else is able to pick up the pieces and carry on the maintenance.
With closed source software, if the maintainer disappears, the software ceases to be usable in a very short time.
Not to mention that if one person/group develops an app/distro, and another person/group wants to make modifications, (s)he/they can create a fork (modification) of it, provided the original work’s credited/acknowledged.
This leads to not only longevity, but evolution. In other words, FOSS projects tend to morph, evolve, and diversify over time, getting better, and more varied with each evolutionary change/step. While a similar evolution can occur with proprietary projects, the process is much slower, and limited, because it’s driven more by profit than user input.