Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)GV
Ganesh Venugopal @ Subject6051 @lemmy.ml
Posts
68
Comments
392
Joined
2 yr. ago

  • hey lsmod gave these results

     
        
    Module                  Size  Used by
    uvcvideo              131072  0
    videobuf2_vmalloc      20480  1 uvcvideo
    videobuf2_memops       20480  1 videobuf2_vmalloc
    videobuf2_v4l2         36864  1 uvcvideo
    videobuf2_common       73728  4 videobuf2_vmalloc,videobuf2_v4l2,uvcvideo,videobuf2_memops
    videodev              290816  3 videobuf2_v4l2,uvcvideo,videobuf2_common
    mc                     69632  4 videodev,videobuf2_v4l2,uvcvideo,videobuf2_common
    usbcore               344064  6 xhci_hcd,cdc_acm,uvcvideo,btusb,xhci_pci
    usb_common             16384  3 xhci_hcd,usbcore,uvcvideo
    
      

    I have listed everything which has uvc in it

  •  
        
    $ find /lib/modules/$(uname -r) -type f -iname "*uvc*"
    /lib/modules/6.0.0-6mx-amd64/kernel/drivers/media/usb/uvc/uvcvideo.ko
    /lib/modules/6.0.0-6mx-amd64/kernel/drivers/usb/gadget/function/usb_f_uvc.ko
    
      

    This it? Is this not driver error then?

    edit:

    This made me think I needed a driver. Last virtual camera driver thing

  • The DE is the limiting factor here. MX uses XFCE, which does not yet support Wayland. For that, you’ll need to use KDE Plasma or Gnome. The former requires an additional wayland session package to be installed, while Gnome comes with it by default.

    You could create a new user session, install whichever one you prefer and then see if that works with Waydroid.

    I guess it saved me that I yesterday installed Gnome de (on my MX xfce 21) and today I was able to successfully install Waydroid!

  • I used Windows exclusively for 10+ years, and I still have to use it at work, but for me the experience is the opposite… Windows regularly causes issues, and it usually takes a lot of effort fixing them because it doesn’t give useful error messages and due to the OS’ proprietary nature. Almost every week some Teams meeting is delayed because some participant’s sound is suddenly not going to their headset. Another frequent problem I have at work is that networking for the virtual machines stops working either fully or partially, and IT’s solution is “just reboot your computer when that happens”. Or when I upgrade my computer, and Windows refuses to authenticate despite me having a valid serial number. At least Microsoft used to have good support that you could chat with, but it seems like they’ve replaced that with some interactive troubleshooter app (which btw. didn’t solve my issue, redirected me to a different online troubleshooter which eventually redirected me back to the first troubleshooter).

    That’s not saying that I never have issues on Linux, but at least for me those are generally much easier to fix.

    that's a very interesting point of view. I have faced the issues you are mentioning before, but I thought it was a hardware issue and it would go away with good hardware. Apparently not. Lack of actual error messages (with good details atleast) seems to be a very valid concern.

    thank you for your comment, seriously, this was an interesting take.