Solaar VS weywot

If it's got the Logitech unifying receiver, it won't work outta the box. You gotta download Solaar

- Solaar: Device manager for Logitech devices (connected via Unifying, Bolt, Lightspeed or Nano receivers + some connected via USB cable / Bluetooth)

from: https://pwr-solaar.github.io/Solaar/

Depending on your mouse, Solaar could do the job. I use it in combination to trigger Fly-Pie.

Now moving on to the Linux part. Do you use gnome/kde? Or some tiling DE? I use Solaar and it's lovely! M720 has a perfectly placed gestures button. I use it to move my windows to left/right monitors and switch between upper/lower desktop spaces. The gesture button works flawlessly when you set up solaar correctly.

I've been beating my head against the wall trying to figure out why this isn't working as I expect. I'm trying to make a user service to run solaar so that my logitech mouse's scroll wheel behaves like I want without having to open the app manually. The software itself provides a .desktop file for autostart, and I used this as a basis.

I've used Solaar for my MX Master 3, works great. https://pwr-solaar.github.io/Solaar/

We don't officially support wireless keyboards or mice for infosec, environmental, and supportability reasons. But if we had to, the established Logitech Unifying and newer Logitech Bolt ecosystem allow for ready re-pairing of dongles with peripherals. Logitech Unifying is fully functional under Linux with solaar from your distro's repos. You have to be astute when buying, to always look for a picture of the dongle with the orange Unifying logo or the safety-yellow Bolt logo, however. If the logo isn't on the packaging or in the promo picture, I can assure you that you will not get a Unifying or Bolt dongle.

Have you tried Solaar?

WeyWot's GitHub has many great guides ( https://github.com/spxak1/weywot )

So you press F9 or F12 and boot from the bios selection ? No problems that is the easiest method, and recommended, but if your having problems you could try this https://www.youtube.com/watch?v=4idr6sXSue0&list=PLS_d8s-cLQwWWLePiVWve1X-_YP6YrwRU&index=10 this is rEFInd easy to setup and maybe it will solve your boot problem, then you will know it is something to do with the Bios boot, and lastly, probably the most difficult duel boot is editing the systemd bootloader of Pop_OS https://github.com/spxak1/weywot/blob/main/Pop_OS_Dual_Boot.md approach with caution, you could lose the ability to boot either system if you make a mistake.

Das schon mal ausprobiert: https://github.com/spxak1/weywot/blob/main/Pop_OS_Dual_Boot.md ?

Please check this

I currently am trying to dual boot pop os and windows. I have them in separate drives. Yesterday I was following the steps provided by this GitHub https://github.com/spxak1/weywot/blob/main/Pop_OS_Dual_Boot.md. After running windows though the systemd option disappeared from my boot menu. I booted into a live disk to try and see if I could find the drive but only my drive with windows shows up. What do I do?

Refer this

Don’t throw windows out, it can be useful, I’d recommend dual booting. For the distro, I’d go with Fedora (Workstation) or PopOS. Fedora’s hard to break and reliable as well as easy to dual boot (guide) while PopOS is Ubuntu based so it can draw from Ubuntu’s giant popularity, but it’s not the easiest to dual boot (guide)

Using a more sophisticated method, like ed2k is preferred if you can. There is also this.

In many guides and other post I see people copying the EFI Windows folder similar to this github on a boot partition of approximately 1GB. But the arch wiki recommends installing the package ed2k and mapping a script to boot directly from the Windows EFI.