IceVAN

joined 11 months ago
[–] IceVAN@beehaw.org 1 points 1 month ago* (last edited 1 month ago)

I got these: Moko foldable and Plugable bluetooth. I highly recommend the second one because 1. Normal layout and 2. It works with usb cable, so you can unlock LUKS or get into bios if you need to. The moko feels better to type on but you have to deal with the layout (just give it time) and it only works via bluetooth (usb is charge only), so no LUKS prompt/bios AFAIK.

[–] IceVAN@beehaw.org 3 points 2 months ago* (last edited 2 months ago) (2 children)

I got a wacom intuos s (pug & play) for that reason, after having a couple of huions. Opentabletdriver only gave me problems (constant crashes and unstable functionality). I'd recommend you a foldable bluetooth keyboard for jams (check for one that work in usb mode too if you want to input the luks password or something like that). I've been using the deck as main pc for the last 6 months or so with debian, docked most of the time. Not a bad setup for the money.

[–] IceVAN@beehaw.org 1 points 7 months ago* (last edited 7 months ago)

Gimp just released 3.0 rc1.

 

Hi, I'm in the process of installing a standard arch distro on the deck with the idea of using the deck as my main pc for daily use giving preference to the desktop session and with a standard type of installation instead of an immutable one (among other things, I need luks and custom udev rules). I have openbox working.

The idea is to have a X11 session with openbox, a Wayland session with Labwc and lastly the gamescope/steam UI session and just switch between them via SDDM.

I added the steam jupiter repo to install the jupiter-fan-control package. I was wondering what other packages I should install besides the fan-control.

Any ideas?. Thanks!.

[–] IceVAN@beehaw.org 2 points 9 months ago

I had that warning too with a r9 270x and if I remember correctly it was because radv didn't have official/full support for GCN =<2, so what they're saying is something in the line of... it may break. In my case, it worked beautifully gaming with proton, etc.

[–] IceVAN@beehaw.org 1 points 9 months ago

You're right, I don't have mint/ubuntu installed nor that kind of hardware (anymore), so I can't give precise instructions. I was just like: see that you're not missing any of these packages/repos/firmware and adapt it to your needs. I had to deal with a laptop with dual gpu (intel+amd) and it was such a pain in the ass to get it working. I think you needed to have n packages installed, add grub flags, configure X11 to use amdgpu and blacklist radeon and even when I had it working, the amd gpu was only compatible with a limited amount of vulkan instructions so I had graphical glitches and games breaking. Old dual gpu setups are just a nightmare.

[–] IceVAN@beehaw.org 1 points 9 months ago (3 children)

You need to activate contrib, non-free, non-free-firmware repos: sudo nano /etc/apt/sources.list You should have something like deb http://URL_OF_THE_REPO DISTRIBUTION main, you need to add contrib non-free non-free-firmware to the end of those lines like: deb http://URL_OF_THE_REPO DISTRIBUTION main contrib non-free non-free-firmware then you do sudo apt update and try installing the packages again.

[–] IceVAN@beehaw.org 1 points 9 months ago* (last edited 9 months ago) (5 children)

This is the setup I use in debian, it might give you a hint (no PPAs, standard repos):

sudo apt install mesa-vulkan-drivers mesa-vulkan-drivers:i386 libvulkan1 libvulkan1:i386 vulkan-tools vkd3d-demos mesa-opencl-icd clinfo libxrandr2 libxrandr2:i386 libvulkan-dev libvulkan-dev:i386 libgl1-mesa-dri libgl1-mesa-dri:i386 vkmark glmark2-x11 firmware-amd-graphics radeontop xserver-xorg-video-amdgpu