Bonjour,
I downloaded garuda-dr460nized-linux-zen-220428.iso some time ago. I admired the beauty, originality and user-friendliness of the OS and managed to install it without any problem on my Asus R753U, but the full system update was only partial due to an "unsolvable" conflict... Result: the computer had to be shut down using the button.
I just downloaded the garuda-dr460nized-linux-zen-220717.iso version. And there, no more conflict but the installation stucks at 79% while configuring hardware.
It is with regret that I give up, waiting impatiently for this problem to be solved and for it to be possible to enjoy this OS "out of the box".
Notes: I had a lot of trouble to register because the many confirmation mails were not arriving in my usual mailbox (xxxx@free.fr). I had to provide a gmail address!
I didn't find the way to preview this message before sending it!
Thanks to the Garuda team who does a wonderful job.
Regards
If you're having problems with Hardware configuration, boot using open source drivers when you launch the ISO and install the drivers later with the setup assistant.
Also please: 1. send the error message you had when you tried updating (we can't read your mind)
And 2. Send your garuda-inxi as requested in the template. The template is meant to be used, not ignored.
Hello TNE, thank you for your answer.
I have of course tried with the free as well as with the non-free drivers, but the outcome is the same.
(we can’t read your mind)
…All in good time!
Send your garuda-inxi as requested in the template.
What do you exactly mean?
Here is the error message while updating the system:
:: Starting full system upgrade...
warning: kvantum-theme-sweet-git: ignoring package upgrade (r254.b9dae16-1 => r269.6e058fc-1)
:: Replace kwayland-server with extra/kwin? [Y/n] y
:: Replace lib32-sdl with multilib/lib32-sdl12-compat? [Y/n] y
:: Replace qemu with extra/qemu-desktop? [Y/n] y
:: Replace qemu-arch-extra with extra/qemu-emulators-full? [Y/n] y
:: Replace sdl with community/sdl12-compat? [Y/n] y
:: Replace wxgtk-common with extra/wxwidgets-common? [Y/n] y
:: Replace wxgtk3 with extra/wxwidgets-gtk3? [Y/n] y
resolving dependencies...
looking for conflicting packages...
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: wireplumber and pipewire-media-session are in conflict
Press enter to exit
â•â”€garuda@garuda in ~ as 🧙
╰─λ garuda-update
:: Synchronizing package databases...
garuda is up to date
core is up to date
extra is up to date
community is up to date
multilib is up to date
chaotic-aur is up to date
--> Refreshing mirrorlists using rate-mirrors, please be patient..
:: Synchronizing package databases...
garuda 75.3 KiB 49.0 KiB/s 00:02 [------------------------------------] 100%
core 157.0 KiB 135 KiB/s 00:01 [------------------------------------] 100%
extra 1715.3 KiB 181 KiB/s 00:09 [------------------------------------] 100%
community 6.7 MiB 302 KiB/s 00:23 [------------------------------------] 100%
multilib 170.8 KiB 112 KiB/s 00:02 [------------------------------------] 100%
chaotic-aur 1973.4 KiB 258 KiB/s 00:08 [------------------------------------] 100%
spawn pacman -Su sweet-theme-full-git --ignore sweet-kde-git,sweet-cursor-theme-git,kvantum-theme-sweet-git,sweet-gtk-theme-dark,plasma5-theme-sweet-git
:: Starting full system upgrade...
warning: kvantum-theme-sweet-git: ignoring package upgrade (r254.b9dae16-1 => r269.6e058fc-1)
:: Replace kwayland-server with extra/kwin? [Y/n] y
:: Replace lib32-sdl with multilib/lib32-sdl12-compat? [Y/n] y
:: Replace qemu with extra/qemu-desktop? [Y/n] y
:: Replace qemu-arch-extra with extra/qemu-emulators-full? [Y/n] y
:: Replace sdl with community/sdl12-compat? [Y/n] y
:: Replace wxgtk-common with extra/wxwidgets-common? [Y/n] y
:: Replace wxgtk3 with extra/wxwidgets-gtk3? [Y/n] y
resolving dependencies...
looking for conflicting packages...
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: wireplumber and pipewire-media-session are in conflict
I’d first focus on the installed system rather than on why the new iso is stuck at HW detection, since if we’re able to fully update your current system you won’t need the new iso anymore (this is a rolling release).
This conflict is very strange, because it should be detected and solved by garuda-update removing the latter:
Maybe this is an old system (not updated since a while). It might help seeing the garuda-inxi of the installed system, not only the one from the live USB. Anyway, garuda-update should self-update as first step, that’s why it is strange.
To cut it short, we could resolve the conflict manually with:
Bonjour,
... I finally managed to do an installation with a complete system update. To do this, I had to use the oldest (May 28, 2022) of the downloaded isos, because with the most recent one, it was not working as said above. And this took several hours and three successive steps during which the update improved without being completely successful.
Strange indeed!.
3 months... So old?
Thank you all for your patience and good guidance.
O dear, system failed to shutdown. Had to use the laptop button (see picture). At reboot, Octopi freezes while trying to install Gimp, could even not send this message from Firedragon which "is already running" but doesn't display its window.
Linuxian for more than 10 years, maybe I'm a bad Garuda user. I am so sorry...
Before choosing Garuda, I tried and installed MX Linux, Pop!_OS latest versions, both working perfectly. But I lIKE Garuda the best. I think like you that it is a kernel problem that does not support one of the hardware components of my laptop (ASUS R756U).
Most definitely, you sohuld try some other kernels.
Look at this (old) thread. Most likely a different root cause (old kernels) but some similarities.
Normaly it’s worth trying to go bit “back” with the linux-lts kernel and a bit “ahead” (especially in case of very new HW) with linux-mainline or even linux-next
This “guy” leaved the session using the power off button. Then, pressed the “escape” button to see the shutting down process log at 11h00 PM, hardly reset after I got home at 19h00 AM , screen still showing the messages of the picture above. What else could I do?
The system is really disturbed because it doesn't let me create/save the script in /usr/local/bin/magic.sh, even in administrator mode (create new file grayed) and it's suddenly very slow.
Too bad, I'll come back later or try with another laptop... Thanks.
